comment on

Just another idea, which might or might not be applicable in your case.

I too once had the requirement to allow multiline entries (within one field). The CSV tables were written by Excel, so it was possible to set things up such that newlines within-field were \n Unix-style, while the row records were being separated by \r\n Windows-style newlines. That way, I could easily distinguish them, in order to read in one row at a time from the CSV file.

Not sure if you have control over how the CSV files are being generated, but if so, maybe you can arrange for something similar...

Also, personally, I'd use Text::CSV_XS (or some such) to properly split up fields, and then do my manipulations on them... OTOH, I don't want to spoil your fun finding a nice regex solution :)

In reply to Re: Conditional continued matching with regexes by almut
in thread Conditional continued matching with regexes by bart

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Welcome to the Monastery
	PerlMonks