Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: BGB <cr88192@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: question about linker
Date: Thu, 5 Dec 2024 17:32:45 -0600
Organization: A noiseless patient Spider
Lines: 51
Message-ID: <vitd6t$1svqk$1@dont-email.me>
References: <vi54e9$3ie0o$1@dont-email.me>
 <8734j9sj0f.fsf@nosuchdomain.example.com> <vidnuj$1aned$1@dont-email.me>
 <87ttbpqzm1.fsf@nosuchdomain.example.com> <vie0j5$1g968$1@dont-email.me>
 <vieun5$1mcnr$3@dont-email.me> <vihamj$2cflq$1@dont-email.me>
 <vihili$2f79m$1@dont-email.me> <vihu63$2ipg0$1@dont-email.me>
 <vii3kq$2kmc8$1@dont-email.me> <vikqvf$3fhce$1@dont-email.me>
 <jNm3P.7909$XuU6.3431@fx40.iad> <vio9bh$dtmc$2@dont-email.me>
 <fS%3P.63777$vLg2.31641@fx17.iad> <viq4b3$10kq3$2@dont-email.me>
 <_o14P.71646$hspc.53247@fx10.iad> <viqc22$124jc$2@dont-email.me>
 <861pymkvn4.fsf@linuxsc.com> <vit1b8$1qitd$1@dont-email.me>
 <87ttbhzq02.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 06 Dec 2024 00:32:46 +0100 (CET)
Injection-Info: dont-email.me; posting-host="6cb92a3ae3fbeb2cb154fb88460336bf";
	logging-data="1998676"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/OVrLEt3czY7HrJZwMo420M/PePgM7yz8="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:WUj4Vu4yZCLbQVzdR4LT01Yxf2E=
Content-Language: en-US
In-Reply-To: <87ttbhzq02.fsf@nosuchdomain.example.com>
Bytes: 3440

On 12/5/2024 5:09 PM, Keith Thompson wrote:
> BGB <cr88192@gmail.com> writes:
>> On 12/5/2024 9:16 AM, Tim Rentsch wrote:
>>> BGB <cr88192@gmail.com> writes:
>>> [considering .csv files and how to process them]
>>>
>>>> Brings up the thought of how, ASCII has a bunch of control
>>>> characters, but generally only a small number of them are used:
>>>>     \r, \n, \t, \b
>>>>     \e, \a, \v, \f (sometimes / rarely)
>>>>
>>>> For CSV, we used ',' (a printable ASCII character) for something
>>>> that (theoretically) could have used \x1E (Record Separator).
>>> That would have been a horrible decision.
>>
>> Well, ASCII has all of these control characters, with assigned uses,
>> and we use only a few of them...
>>
>> But, yeah:
>> Pros of comma: Easy to type, plain text, ...
>> Cons of comma: AFAIK, CSV files often can't have commas in data fields.
> 
> CSV files *can* have commas in data fields, and there are well-defined
> ways to represent them.  For example, this line has three fields:
> 
>      one,"two,three",four
> 
> And there are additional rules for fields containing quotation marks.
> 
> See <https://www.ietf.org/rfc/rfc4180.txt> for the most widely accepted
> specification.
> 
> Note that RFC 4180 specifies CRLF line endings.  Many of the CSV files
> I've dealt with use LF instead.
> 
>     Encoding considerations:
> 
>        As per section 4.1.1. of RFC 2046 [3], this media type uses CRLF
>        to denote line breaks.  However, implementors should be aware that
>        some implementations may use other values.
> 

OK, looked...

I hadn't been aware that quoting and similar was a thing for CSV files 
(I had previously thought it only supported unquoted fields with the 
comma always being interpreted as a separator).

> [...]
>