News for hackers. Stuff that matters.
Re:So you want to write your own CSV code (2014) by eyelidlessness on Friday May 15, 2020 @10:42AM (#23192729)
It's ambiguous, and this is why significant whitespace can be so frustrating. Unless it's specified, some people will interpret a full-line comment as a blank line with a comment ending it (`^#.$`), and others will interpret it as you have (`^#.?\n`). Neither is obviously correct (even if it's obvious to you).

Edit: I don't know how to escape in HN formatting. Obviously there are italics where literal asterisks should be.

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

  *** You can just use three asterisks. ***
* You can just use three asterisks. *

   Unfortunately you need something after them though. ***
Unfortunately you need something after them though.
Re:So you want to write your own CSV code (2014) by eyelidlessness on Saturday May 16, 2020 @10:26PM (#23208963)
Thanks, that's good to know!
Re:So you want to write your own CSV code (2014) by DoreenMichele on Friday May 15, 2020 @07:16PM (#23198626)
If you indent it two spaces, I think that should solve that problem:

   *(`^#.$`), and others will interpret it as you have (`^#.?\n`)*

(Not sure where you intended those asterisks. I made my best inference.)
Re:So you want to write your own CSV code (2014) by eyelidlessness on Saturday May 16, 2020 @10:27PM (#23208974)
Yeah I was hoping to keep them inline, but indenting surely would have helped. I intended them after the dots (`.*`, dot asterisk in case I get the escaping wrong, is 0 or more characters in regex).