Both kill and sliplogin, which were converted to use this array, are
either specified to use, or have traditionally used, upper case names.
This change shouldn't have bad side-effects, sys_signame is new to netbsd
and nothing in the source tree except kill and sliplogin use it.
These may be "good enough" for big-endian systems that do not have assembly
language versions of their own. A compiler should be able to do a fairly
good job optimising them, it probably won't be smart enough to omit the
stack frame, but then again, these functions won't be called unless the
macro versions are undef'd.
On the other hand, they are only intended for bootstrap purposes on little-
endian systems. They should be replaced with assembly language versions as
soon as possible.
Don't bother clearing %eax in bcopy(), it doesn't return anything so
why clear a return value that never gets used?
Don't bother clearing direction flag. Any code that doesn't set/clear
it explicitly before a string instruction deserves to loose.
"Some historical implementations either block or ignore the signals
SIGINT, SIGQUIT, and SIGHUP while waiting for the child process to
terminate. Since this behavior is not described in POSIX.2, such
implementations are not conforming."
received complaints about using shorts in the table (but i need a range
of -1..255), so now the tables will not be used unless either toupper()
or tolower() (and soon, setlocale()) are used. This can save up to 514
bytes.
In toupper_.c and tolower_.c make sure that our assumption of EOF == -1
holds.
Fixed bug where _toupper_tab_ was initialized pointing to _C_tolower_tab.
The tables have been renamed to _C_ctype_, _C_tolower_, and _C_toupper_
as they are tables for the C locale. When switching to a new locale, the
pointers will be set to point to tables specific to the new locale.
that -1 is returned when the fork fails. Updated implementation to
use int rather than deprecated "union wait". Updated documentation
to describe error / return values.
format modifiers that are needed for a 1003.2 compliant date(1). The
modifiers don't actually do anything at present and are not documented.
It's too confusing to the user to describe localization features when
they aren't implemented yet. It is safe to do this, as the modifiers
fall back to the default behavior if the locale doesn't support alternate
eras or numeric formats.
But, in anticipation of _some_ locale support, all month and day names and
abbrevs, certain time formats, am/pm, etc. are now accessed through variables.
