Awk: `Begin { ` Part 1

Re:Awk: `Begin { ` Part 1 by necheffa on Friday October 30, 2020 @09:57AM (#24942221)

Everything you just described seems like reasons to not use CSV files in general, rather than not use AWK on CSV.

[ Parent | on HN ]

Re:Awk: `Begin { ` Part 1 by sidpatil on Friday October 30, 2020 @10:01AM (#24942256)

I'm disappointed we didn't use ASCII-separated values.

https://news.ycombinator.com/item?id=7474600

[ Parent | on HN ]

Re:Awk: `Begin { ` Part 1 by nmz on Friday October 30, 2020 @01:43PM (#24944850)

And apparently an even better solution is just putting the size in the format itself. No need to parse when you can just seek.

https://blog.kowalczyk.info/article/fc9203f7c72a4532b1ae51d0...

[ Parent | on HN ]

Re:Awk: `Begin { ` Part 1 by protomyth on Friday October 30, 2020 @05:40PM (#24947139)

Did it multiple times and it works great, but companies you send raw data to often get huffy. So, back it goes into CSV or some poorly defined fixed width text file.

[ Parent | on HN ]

Re:Awk: `Begin { ` Part 1 by im3w1l on Friday October 30, 2020 @05:47PM (#24947189)

I don't see what issue they solve. You still need escaping, because eventually you will want to put an ascii-separated value into your spreadsheet.

[ Parent | on HN ]

Re:Awk: `Begin { ` Part 1 by smallnamespace on Friday October 30, 2020 @01:21PM (#24944575)

CSV is the default interchange in many fields (e.g. a lot of machine learning or academia). You don't get to choose what formats your colleagues send to you.

[ Parent | on HN ]