FreeCalypso > hg > freecalypso-tools
view rvinterf/include/ffslimits.h @ 465:003e48f8ebe1
rvinterf/etmsync/fsnew.c: cast 0 to (char *) for execl sentinel
I generally don't use NULL and use plain 0 instead, based on a "NULL
considered harmful" discussion on the classiccmp mailing list many aeons
ago (I couldn't find it, and I reason that it must have been 2005 or
earlier), but a recent complaint by a packager sent me searching, and I
found this:
https://ewontfix.com/11/
While I don't give a @#$% about "modern" systems and code-nazi tools,
I realized that passing a plain 0 as a pointer sentinel in execl is wrong
because it will break on systems where pointers are longer than the plain
int type. Again, I don't give a @#$% about the abomination of x86_64 and
the like, but if anyone ever manages to port my code to something like a
PDP-11 (16-bit int, 32-bit long and pointers), then passing a plain 0
as a function argument where a pointer is expected most definitely won't
work: if the most natural stack slot and SP alignment unit is 16 bits,
fitting an int, with longs and pointers taking up two such slots, then
the call stack will be totally wrong with a plain 0 passed for a pointer.
Casting the 0 to (char *) ought to be the most kosher solution for the
most retro systems possible.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Mon, 11 Feb 2019 00:00:19 +0000 |
parents | e7502631a0f9 |
children |
line wrap: on
line source
/* * Limits on FFS filenames and pathnames * * The deepest pathname allowed is one of the form /1/2/3/4/5/6, where the * last component may be a file, a directory or a symlink; if this last * component is a directory, it has to be empty, because any child of * that directory would violate the depth limit. * * The proper FFS pathname form begins with a slash (all pathnames must * be absolute, no Unix processes in the fw means no current directories), * has exactly one slash in each separating place (no double slashes), * and no trailing slash except in the special case of the root directory, * whose full pathname is "/". * * Each component name is [1,20] characters long; combining this limit * with the maximum depth of 6 puts the maximum length of a properly-formed * full pathname at 126 characters. */ #define MAX_FN_COMPONENT 20 #define MAX_NAME_DEPTH 6 #define MAX_FULL_PATHNAME ((MAX_FN_COMPONENT+1) * MAX_NAME_DEPTH)