Problem: this is malformed CSV. This is also in contradiction with example 7. Also in CSV notation, this would mean that the string is continuing on the next line which is also accepted.
Of course, I knew some of them are malformed CSV format. But I'd like to have a smart parser which its behavior can be set trough some properties/parameter. So, I can decide whether I'll accept some malformed format or make it strict.
John Doe;"123 My Street SomeTown, Some Country Some area code";Other information
I never knew a single CSV record can be splitted into some lines. I hope this is a very rare situation. :)
The above is one record but spam on 3 lines. Now you can't solve 4 and 5 and 6 without breaking the logic of someone else. This is why I tried to be error checking be keep normal CSV logic. I do allow a record on many lines.
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.
In attachment the last version of the code. This is released under the same licence as FPC unit fcl/rtl.
I still don't need widestring and pchar support for this moment. A normal pascal string would be enough for me. :)
Thank you. I'll try this one too. :) -Bee- has Bee.ography at: http://beeography.wordpress.com _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
