Re^2: Best way to parse multiline data?

Don't slurp 600M - that translates to roughly 3G+ of RAM.

Not if you slurp to a scalar.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco.

Rule 1 has a caveat! -- Who broke the cabal?

Comment on Re^2: Best way to parse multiline data? Download Code

Replies are listed 'Best First'.
Re^3: Best way to parse multiline data? by dragonchild (Archbishop) on Apr 18, 2005 at 12:36 UTC
It's still 600M + 41 bytes. :-) My wife's blog	[reply]