background threads don't step on eachother (as well as error reports and status
messages).

additional args passed to load(), or B) it's a background-loaded script
(in which case we always define argv now as well).
This fixes the Deuce-reported bug:
"When chat_sec.js calls irc.js, argc is apparently zero."

(i.e. msgbase.get_msg_header() returns null).

log() implementations are generally thread-safe, so this should be okay.
Requested by Cyan.

the values with references to the original context weren't "copied" into the
newly-created background context, so Strings, objects, and doubles would cause
problems (e.g. crashes). Passing objects and array is still not supported, but
at least it won't crash now. Found by Cyan.

passed).

SDL-exec problem seen in sbbs and jsexec. SDL is disabled by default now.

"All") and remove this piece from the subject (> 25 char subjects gets
truncated overt QWK).

the ability of external programs to disconnect the socket (hangup).

this and do *not* write to the hungup.log file.

and virtual UART VDD.
Use FOSSIL function constant macros from fossdefs.h.

and virtual UART VDD.
New hangup named event, for VDD to use to disconnect socket at program's
request (dropped DTR).

and virtual UART VDD.

* irclib IRC_string() function now behaves exactly like every other IRCd in
  the world, and requires the "arg" argument, which defines which word to
  begin scanning at in the string.
* irclib IRC_match() is now obsolete thanks to DigitalMan's wildmatch()
  function in Synchronet 3.14 -- all IRC_match() functions in the IRCd now
  switched to wildmatch()
* More general cleanups and optimizations.

  does it.