Re: question about linker

On 12/4/2024 12:43 PM, Scott Lurndal wrote:

Bart <bc@freeuk.com> writes:

On 04/12/2024 16:57, Scott Lurndal wrote:

Bart <bc@freeuk.com> writes:

On 02/12/2024 18:13, Scott Lurndal wrote:

Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:

On 01.12.2024 17:42, Bart wrote:

On 01/12/2024 15:08, Janis Papanagnou wrote:

On 01.12.2024 12:52, Bart wrote:

>

makes typing easier because it is case-insensitive,

>
I don't think that case-insensitivity is a Good Thing. (I also don't
think it's a Bad Thing.)

>
I think it's a _real bad thing_ in almost every context related
to programming.

>
OK. I think the opposite. So who's right?

>
The consensus so far does not favor your viewpoint.
>

From the languages I know of in detail and I'm experienced in none
is "fussy" about semicolons. Rather it's a simple and well designed
syntactical token, whether used as separator or terminator. You've
just to put it where it's defined.

>
Indeed.  One wonders at Bart's familiarity with formal grammars.

>
Why?

>
Because having a formal grammar is the keystone of a good
language design.
>

>
Do you use a formal grammar when parsing a CSV file, or something
equally trivial?

 I don't parse csv files, there are dozens of tools already
available to perform that action for me with no need
to reinvent the wheel.
 for example, cvstool comes with most linux distributions:
 https://github.com/maroofi/csvtool

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).
Though, almost seems like one could make a case for reclaiming a lot of these for special-case printable characters.
Or, say, (10..19, 0E..0F, 1C..1F):
Repeat a recently-seen non-ASCII code-point for UTF-8.
Though, likely only relevant in certain contexts (like compacting UTF-8 strings).
...