so their fts_accpath members no longer have the correct relative
path. We can solve this problem by looking at the parent's path
via p->fts_parent->fts_accpath.
Added BACKWARDS directive to Makefile for compatibility.
Completely changed the name space as per FSF's request.
Fixed a line-addressing bug introduced by previous `fix', i.e.,
space preceding a digit acts a plus (+) operator, as in `1 1' == `2',
and a plus operator by itself acts as +1, but a space by itself
should not equal a plus operator, i.e., `1 ' != `1+' == `2'.
If all the arguments have a "." or ".." basename, the exit value should be
modified whether or not the -f flag was specified.
Don't exit if a file can not be read or there is another error (FTS_DNR or
FTS_ERR), there are probably other files that we can process successfully.
to be a locale specific regular expression. This change hard codes POSIX
locale behavior, and will be replaced by a locale independant equivalent
as soon as locales are fully implemented.
Some reordering and modifications in the Makefiles for sh, dump,
restore to get dependicies right. The README in /usr/share/mk
states that it's a Bad Thing(tm) to add something after
.include <bsd.prog.mk>, but this seems the only way to get the
dependencies right.
to be a locale specific regular expression. This change hard codes POSIX
locale behavior, and will be replaced by a locale independant equivalent
as soon as locales are fully implemented.
had time to look at the recursive code, but it probably has the same
types of problems.
Added code to set the default locale, so it will work correctly when
our locale code is more than just stubs.
Added prototypes, etc. to make gcc -Wall happier.
Added and/or operator test to POSIX special case processing, so now:
$ test ! "abc" -o "abc"
evaluates to true.
The correct fix is probably to yank the superfluous special case code, but
I don't have time to verify the correctness of the result.
