8dc92fbd6c
The HLP-changes to sbase have been a great addition of functionality, but they kind of "polluted" the enmasse() and recurse() prototypes. As this will come in handy in the future, knowing at which "depth" you are inside a recursing function is an important functionality. Instead of having a special HLP-flag passed to enmasse, each sub- function needs to provide it on its own and can calculate results based on the current depth (for instance, 'H' implies 'P' at depth > 0). A special case is recurse(), because it actually depends on the follow-type. A new flag "recurse_follow" brings consistency into what used to be spread across different naming conventions (fflag, HLP_flag, ...). This also fixes numerous bugs with the behaviour of HLP in the tools using it. |
||
---|---|---|
.. | ||
agetcwd.c | ||
apathmax.c | ||
concat.c | ||
cp.c | ||
crypt.c | ||
ealloc.c | ||
enmasse.c | ||
eprintf.c | ||
eregcomp.c | ||
estrtod.c | ||
fnck.c | ||
getlines.c | ||
human.c | ||
md5.c | ||
mode.c | ||
putword.c | ||
recurse.c | ||
rm.c | ||
sha1.c | ||
sha256.c | ||
sha512.c | ||
strcasestr.c | ||
strlcat.c | ||
strlcpy.c | ||
strsep.c | ||
strtonum.c | ||
unescape.c |