On 7/6/06, Bisma Jayadi <[EMAIL PROTECTED]> wrote:
As I said, the CSV parsing logic can be tuned. :) But, it must able to solve all
malformed format possibilities first (at least most of them). The actual
behavior then can be set.
Thinking a bit more about it. I don't known if allowing malformed CSV
is a good idea. Where do you draw the line with what is acceptable?
Also, I can't think that you can create a parser that can handle all
forms of malformed CSV at the same time...
I don't think you should treat the symptom, but rather the underlying
cause of the problem. A better approach will be to let the parser
report on issues found and let the person/company who created the CSV
file know that their CSV generator is broken and should fix it.
Regards,
- Graeme -
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
