So you want to write your own CSV code (2014)

Re:So you want to write your own CSV code (2014) by r00fus on Friday May 15, 2020 @12:41PM (#23194202)

If the ASCII separators were supported regularly in text editors since the early days then it would remove 90% of the problems.

I prefer the | pipe character as a delimiter - easy to see, not part of common speech or titles, and enterable via keyboard. Yes, it can exist in the field but less likely.

[ Parent | on HN ]

Re:So you want to write your own CSV code (2014) by niccl on Friday May 15, 2020 @05:33PM (#23197734)

But if it _might_ turn up, you have to assume it will and deal with it, and then you're into the exact same problem as before, but with something even less 'standard' than before.

I think it's like cryptography. Why bother to roll your own when there are people who are cleverer (certainly than me. I don't know about you) who've already put a lot of effort in to this, so just use one of the well tested standard libraries and don't mess with it

[ Parent | on HN ]

Re:So you want to write your own CSV code (2014) by r00fus on Friday May 15, 2020 @07:03PM (#23198532)

I'm not recommending "rolling your own". You still use CSV libraries, but with a pipe delimiter instead.

[ Parent | on HN ]

Re:So you want to write your own CSV code (2014) by chapium on Friday May 15, 2020 @12:58PM (#23194421)

It looks a LOT like l and I.

[ Parent | on HN ]

Re:So you want to write your own CSV code (2014) by r00fus on Friday May 15, 2020 @05:30PM (#23197701)

Luckily code sees it as ASCII 124. If you're saying that for compliance, | can be converted to l/I then it's a feature, not a downside.

[ Parent | on HN ]