First attempts at logging via pipe/mailslot.

  really bad things(tm) with bits in channel modes.  Hopefully I've got it
  right this time.
* Updated supported usermodes on the 004 numeric.
* Updated this.get_usermode() to return the proper usermodes, and whether or
  not we're showing the 'broadcast' modes or not.
* Moved ban stuff out of affect_mode_list() because it's totally different
  than setting + or - o/v.
* CHANLIST_X is now all gone, it was ugly and introduced duplication everywhere
* MODECHAR is gone, too, replaced by MODE[CHANMODE_BIT].modechar
* +/- k/l wasn't working as expected (never -k without args, always allow +l
  with args if different than current limit, and allow -l without args.)
* Fixed a nasty bug courtesy of the old DALnet #square regulars involving the
  bits not being checked right.  Doing +o over and over would just flip the
  bit continuously.

Fixed bcc compile warning (SOCKET* != int32*).
Created new global method: dir_freespace() to return the amount of free disk
space for any directory.

to stop the backup process if any single-file backup fails.

* It turns out umode +g isn't oper-only, so let regular users use it.
* Use new function "globops" for sending of globops.
* Make GLOBOPS require oper status in addition to being +g
* A '0' passed to /WHO is the same as a '*' for ircI historical reasons.
* INVITE wasn't propagating down to the user correctly.

* Opers with a small o in their O:Line flags were being propagated as a big O
* New command line option -x is for 'network debug' which will verbosely spit
  out synch info to the network via GLOBOPS.  This will spam a network like
  crazy, so please don't use it unless you've been instructed to.  This is to
  assist in debugging of misbehaving servers (read: software) over the network.
* Rewrote this.setusermode(), because it was a mess.
* Began work on breaking out usermodes into more discrete sections ala Bahamut,
  in particular:
        +w (Users) Allows the user to receive all WALLOPS messages.
        +b (Opers) User may receive CHATOPS messages.
        +g (Opers) User may receive GLOBOPS messages.
        +s (Users) Reception of variou server messages, including KILL.
        +c (Opers) Receive client connecting/disconnecting messages.
        +r (Opers) Receive 'rejected' client messages (i.e. unregd clients)
        +k (Opers) Receive server kill messages.
        +y (Opers) Observe STATS/INFO/LINKS/etc requests for possible abuse.
        +d (Opers) Can receive DEBUG notices.
        +n (Opers) For reception of 'routing' notices.
* Because of this, WALLOPS is now an oper only command.
* Replaced oper_notice() with umode_notice(), which writes out to all users
  of a particular user mode.
* CHATOPS, GLOBOPS, and GNOTICE now all work properly.
* Some appropriate messages are broadcast across the network, including more
  informative server messages (i.e. remote CONNECT, SQUIT, etc.)
* Let other opers know that a user is doing /EVAL.
* Add a kludge for 3.10 machines so that they'll mswait() longer, thus won't
  time out as quickly, hopefully giving them at least a few weeks worth of
  uptime.  The downside to this is that they run slower, alas.  (They probably
  should anyway, considering they don't have select() to throttle CPU usage.)

flags as they relate to QWK-masters and the routing thereof.

* Support complex /LIST syntax.  Similar to Bahamut's in concept, but entirely    different in implementation.  Functions more like complex /WHO, do a /LIST ?
  for usage information.
* Don't show channel topics on +p channels in /LIST.

  /WHO +c @#channel, +#channel, @+#channel, etc.
* New /WHO option: +l <class>, check for users only in a certain IRC class.
* New /WHO option: +t <time>, user has been on for more (+) or less (-) than
  <time> seconds.
* New /WHO option: +I for returning only IP addresses as opposed to hostnames.
--- Ideas for a lot of the new WHO flags came from Bahamut 1.4.36, thanks guys!

HTML pages from ANSI/CTRL-A text.

For use as an external chat pager (alternative to tone/playtone.js).

sbbs->terminated is now a BOOL (instead of bool).

not compatible with a C BOOL (int) pointer, so all js.terminated tests from JS
modules run from the BBS failed (always returned true).

(using JS_ValueToInt32 instead of JSVAL_TO_INT).

offset (which it is not), causing most message index "gets" by offset to fail.

don't proceed to this.work()

added.

(I always wanted to do that commit!)

and for system.clock_ticks

frequency of MSCLOCKS_PER_SEC... the initial value is undefined.