Re: Re: Text::CSV_XS -- Bug or wrong usage?

Could you detail the other Text::CSV_XS bugs you know about please?

I was just beginning to get comfortable with using this module rather than regexes for parsing CSV data given its superior performance over the modules available when I saw the OP's bug. It's a pain, but most of the stuff I am playing with doesn't use escapes never mind escaped escapes so I wasn't too bothered, but if there are more bugs, it would be nice to know what they are.

It would also be useful to know if a) you have reported them to the author. b) what sort of response you recieved if any.

Examine what is said, not who speaks.

1) When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.
2) The only way of discovering the limits of the possible is to venture a little way past them into the impossible
3) Any sufficiently advanced technology is indistinguishable from magic.
Arthur C. Clarke.

Comment on Re: Re: Text::CSV_XS -- Bug or wrong usage?

Replies are listed 'Best First'.

Re: Re: Re: Text::CSV_XS -- Bug or wrong usage?
by diotalevi (Canon) on May 07, 2003 at 13:56 UTC

I tried Text::CSV_XS again and had zero problems. All I can figure is that maybe somewhere along the line it had something to do with seemingly escaped metacharacters. So things like "\\\t" (slash followed by a tab) might have confused it. I do recall that at the time, identical input was in some cases handled by Text::CSV and not handled by Text::CSV_XS though I can't seem to find what the failure mode is just now.

[reply]


laziness, impatience, and hubris
	PerlMonks