Basically, Excel uses the equivalent of ‘file’ (https://man7.org/linux/man-pages/man1/file.1.html), sees the magic “ID”, and decides a SYLK file, even though .csv files starting with “ID” have outnumbered .SYLK files by millions for decades.
Thanks. So I guess the easy compatible solution is to always quote the first item on the first line when writing CSV. Good to know. (Checking if the item starts with ID is more work. Possibly quote all items on the first line for simplicity.) (Reading SYLK is obviously irrelevant, so accepting unquoted ID when reading is the smarter way to go and will actually improve compatibility with writers that are not Excel. Also it takes no work.)
- “Each record is located on a separate line, delimited by a line break (CRLF)” ⇒ editing .csv files using your the typical Unix text editor is complicated.
- “Spaces are considered part of a field and should not be ignored”
- “Fields containing line breaks (CRLF), double quotes, and commas should be enclosed in double-quotes” ⇒ fields containing lone carriage returns or new lines need not be enclosed in double quotes.
Partly because it is fairly fast, partly because, whatever you’re running your language on, chances are better that you can run a C compiler on it than that you can run most other languages.
> In that case how much faster would things be to compile where it doesn't need to filter through hundreds of preprocessor options?
I think most of the time spent isn’t running the preprocessor, but parsing the declarations and definitions.
Regardless, the way to speed up importing definitions in modern C++ is to use #import instead of #include.
https://news.ycombinator.com/item?id=38904758 says they could import the entire std namespace in under a second (that is long when you want to run C++ as a scripting language, but not when you compile large programs)
I suspect disallowing all upper body contact would lead to more goals. Posting a defender on the goal line would be less effective.
> There would probably be quite a bit more acrobatics involved to handle the ball being in the air.
I think that could end up being disallowed, too because of the risk of feet hitting heads, especially inside the penalty area. Think of the body movements of https://en.wikipedia.org/wiki/Sepak_takraw but without the net separating teams.
Treasures are small and rare enough so you can never rule them out completely, but if there were significant amounts of rocks there, we would know because Doggerland has been fairly thoroughly “ploughed” by fishing trawlers and mapped for research (https://en.wikipedia.org/wiki/Doggerland#Discovery_and_inves...)
The geology of the North Sea also indicates “sand” more than “rocks”.
Basically, Excel uses the equivalent of ‘file’ (https://man7.org/linux/man-pages/man1/file.1.html), sees the magic “ID”, and decides a SYLK file, even though .csv files starting with “ID” have outnumbered .SYLK files by millions for decades.
reply