Re: question about linker

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.
But, alas, normal text editors/etc aren't super friendly to uncommon uses of ASCII control codes, so...
Where, say, normal text files only use, say:
   \t, \n, and \r\n for CR=LF files...
Otherwise:
I have noted that incremental AVL tree operations without a parent-node link are too much of a pain.
So (after resuming the implementation effort), I ended up needing to modify my (still incomplete/experimental) filesystem design so that the DirEnt structures have an up-node link, albeit reducing the link size to 20 bits (so, there will be a hard limit of 1M files per directory).
Was initially trying to do it by handling operations like readdir and node rebalancing by tracking the up-link using an internal stack... But, this is too much of a pain.
May also modify the free-list mechanism for free-space management within directories to better deal with searching for multi-entry spaces.
...