CSV vs the # Buffer

Posted by Robert G Laurin on August 07, 2008 at 07:43:25:

I discovered today that when using the 'FILE (#) CSV' command with a INPUT from the # Buffer, the return result is FULLY PADDED with blanks.

I tried something that looked like this:

Data: Format Data$(1),4*252
...
Main:
INQUIRE (C1A,C1A) EXCP=EXCPEOF
FILE (#) CSV
PRINT (#,C1A)
INPUT (#,DATA)
...

And ALL 4 Data$() elements are fully padded to 252. The actual data barely exceeded 300 bytes.

I also already pointed out (in another post) that the generated CSV record properly parsed everything except it did not strip trailing blanks from string fields. Numbers are properly stripped with leading minus sign. Strings containing either a quotation mark (") or a comma (.) are properly handled.

I really like the speed of this new function, beats all the code we had to write & execute in the past.

Follow Ups:

• Re: CSV vs the # Buffer Jon Sacks 10:24:22 08/07/08 (0)
• Re: CSV vs the # Buffer Jim Guerber 09:31:06 08/07/08 (0)
• Re: CSV vs the # Buffer Grant Foraker 08:14:03 08/07/08 (1)
  • Re: CSV vs the # Buffer Stephen Auerbach 06:34:24 08/11/08 (0)

Post a Followup

Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.