not just for Borland.

I'm fed-up with MSVC assertions in ctype functions (e.g. isdigit, isprint, isspace, etc.) when called with out-of-range (e.g. negative) values.

This problem only affects MSVC debug builds, but if you run them (like I do), these things are like little time bombs that can drive you crazy (knocking your board out of service).

The new macros names are bit more descriptive as well.

that don't have strerror_s:
Error: Unresolved external '_strerror_s' referenced from genwrap

Define a thread-safe/re-entrant version of strerror(): safe_strerror() which is just thin wrapper around strerror_s on Windows and strerror_r elsewhere.

builds.

Hopfully this doesn't break the Borland or Watcom (?!) builds.

heavy-handed (performs strdup/malloc's and modifications of the strings),
so a temporary hack is to perform a case-sensitive search (using the standard
strstr() function) first. The results won't exactly match the traditional
strstr() and the performance improvement is only for positive matches
(where the correct case was guessed in the passed 'needle' string arg).
TODO: re-write or copy a good/fast strcasestr() implementation for Win32 builds.

the number of decimal places in the resulting string.

Created byte_estimate_to_str(), much like byte_count_to_str(), except the
byte count is rounded to the nearest tera/giga/mega/kilo-byte
(technically tebi/gibi/mebi/kibi-byte, but ugh, I'm old-sk00l!).

With the supported compilers, we can't rely on the return value of snprintf()
and historically have replaced it with safe_snprintf().  For macOS however,
snprintf() is apparently a macro, not a function, so gendefs.h throws and
error due to redefinition.

Rather than hack around on that, just ensure that we never use the return
value of snprintf() and use safe_snprintf() to ensure we know what the
return value will be.

then a clarifying or modifying word (year[s], month[s], day[s], etc.).
parse_byte_count() and parse_duration() now support a space between the
numeric value (decimal digits) and the modifier. Hopefully this doesn't break
anything, but it makes parse_duration() compatible with the strings generated
with duration_to_vstr(). We might want a verbose version of byte_count_to_str()
in the future, so I figured it made sense to go ahead and add the white-space
skipping/parsing to prase_byte_count() now.

that have standard C mnemonics.

ala Synchronet text.dat) by default and octal format only if
C_UNESCAPE_OCTAL_SUPPORT is defined.
\X## is no longer supported (must use the C-standard \x##
Only 2 hex digits are now supported, longer streams of valid hex digits will
not be parsed as a literal character (unlike the C standard)

of parse_byte_count() and parse_duration()) and use them in ini_file.c

(or possibly intervals) in seconds or fractions of a second. Supports
multipliers: (Y)ear, (W)eek, (D)ay, (H)our, and (M)inute.

rename to parse_byte_count(), so we can use it more places (e.g. jsexec).

Windows 8.0, a.k.a. NT v6.2 instead of Windows 8.1, a.k.a. NT v6.3) by using
a LAN manager API function. Ugh.

Resolve: warning C4244: '=' : conversion from 'double' to 'int', possible loss of data
Fix c_escape_str() handling of "\x00" and "\x01"

future travellers.

(i.e. \r\n or \n) of original text, rather than converting to \n-terminated.

(ie: PDWORD)to satisfy MinGW

after test of n.

Remove potential for undefined behaviour (INT_MIN-1) by making limit an
unsigned long.

systems with chars larger than 8 bits.