I agree with the general statement, but anybody who thinks that
parsing CSV (specifically) is trivial hasn't read the full CSV spec...
in the *full* case, since it has disparate escape sequences for
different scenarios (such as quoted and unquoted, multiline, etc) it
can be just painful. And don't forget that some internationalisations
of CSV apps use semicolon instead of comma by default (Excel in French
IIRC). If you know that you only use a subset of the spec then you can
get away with simpler options like Split- and Regex-based solutions.
The codeproject link I posted claims to deal with most scenarios
including choice of delimiter (I'm not vouching for the code, but
looks useful).
Similar to parsing an e-mail address; sounds easy in the
(E-Mail Removed) sense, but soon gets scary if you really read
the spec... comments... folding whitespace... uri endpoints (e-mail
addresses without an @), etc...
Marc