Re: Is there any regex limitation?

Replies are listed 'Best First'.
Re^2: Is there any regex limitation? by Jim (Curate) on Jul 24, 2011 at 16:34 UTC
You can't use split to parse CSV records—at least not the general form of CSV records represented in benlaw's example. It won't work.	[reply]
Re^3: Is there any regex limitation? by Anonymous Monk on Jul 24, 2011 at 18:01 UTC
You can't use split to parse CSV records—at least not the general form of CSV records represented in benlaw's example. It won't work. Actually yes you can Using split as I've shown is as-good as benlaws intended solution, with the benefit of no backtracking But its a solved problem, so Text::CSV or Text::xSV	[reply]
Re^4: Is there any regex limitation? by BrowserUk (Patriarch) on Jul 24, 2011 at 18:08 UTC
Actually yes you can No. You cannot. Some of the fields contain embedded commas.	[reply]
Re^5: Is there any regex limitation? by Anonymous Monk on Jul 24, 2011 at 18:54 UTC
Re^6: Is there any regex limitation? by BrowserUk (Patriarch) on Jul 24, 2011 at 21:47 UTC
Some notes below your chosen depth have not been shown here
Re^6: Is there any regex limitation? by Jim (Curate) on Jul 24, 2011 at 18:58 UTC
Some notes below your chosen depth have not been shown here
Re^2: Is there any regex limitation? by davido (Cardinal) on Jul 24, 2011 at 22:59 UTC
How does the split solution you posted handle the following portion of the OP's input? `"Wah Woo, Section A"` I can tell you how it does: One field gets (`"Wah Woo`), the next field gets ( `Section A"`), and the embedded but significant comma gets gobbled up. Or to put it simply: It handles it wrong. () parens added to disambiguate whitespace in the example output Dave	[reply] [d/l] [select]
Re^3: Is there any regex limitation? by Anonymous Monk on Jul 26, 2011 at 07:39 UTC
How does the split solution you posted handle the following portion of the OP's input? obviously it doesn't -- just like the OPs actual code use Text::CSV or Text::xSV	[reply]