in load_cfg.c for displaying the path. If you previously had a "parent dir"
configured for a library but did *not* have one or more "Transfer File Paths"
configured for directories within that library, the default location of your
files has now moved! Either clear-out the "Parent Directory" setting or move
your files where SBBS will now expect them to be. Sorry about that.

be sure all necessary dirs are created.

default-setting.
- If a directory's Transfer File Path is not set (blank), and the library
  has a "parent directory" configured, then the default Transfer File Path
  will (now) be <parent>/<dir-code>, where <dir-code> is the directory's
  internal code (lower-cased). This is different from previous behavior where
  the parent dir was not used unless *something* was entered for a dir's
  Transfer File Path. I'm sorry if this brakes your b0rad!
- If a directory's Transfer File Path is not set (blank), and the library does
  *not* hae a "parent directory" configured, then the behavior should be the
  same as before, default Transfer File Path: <data-dir>/<dir-code>
- If a directory's Transfer File Path is already set to a
  full path, there should be no change in behavior either.

Always log the "exiting" line when exiting with a non-zero error level.

These have a large number of optional parameters, so these are placed in
a separate argument as an object:

ie: var s = new ConnectedSocket("synchro.net", "finger", {type:SOCK_DGRAM});
ie: var s = new ListeningSocket(["::","0.0.0.0"], "printer", "spooler", {retry_count:15});

if not unlimited.

- new @-code BPS:x (where x is 0/unlimited, 300, 600, 1200, 2400, ... 115200)
- new JS property: console.output_rate
So you can have mutliple output rate changes in a single file by using multiple
BPS @-codes.
Hopefully this doesn't do weird things with non-compliant terminals.

 -<columns> insert conditional-newlines to force wrap (e.g. -80)
 -newline   append a newline (CRLF) sequence to the output filea

The -<columns> option allows you to take "80-column ANSIs", artwork which
uses 80 columns and assumes the cursor will wrap to the next line
automatically, and insert Ctrl-A/ (conditional-newline) which allows the
file to be viewed nicely on wider terminals. Very cool.

Also added -newline (which can be used multiple times) to append one
(or more) newline sequences to the output file.

Use uppercase for Ctrl-AN and Ctrl-AL when -clear is used.

now accept an optional "count" argument (default: 1).
JS console.backspace() and carrage_return() methods now accept an optional
"count" argumnet (default: 1).

Ctrl-A/0x80+ is no longer supported in message nets (by my decree) so just
use spaces for ultimate compatibility. Synchronet's .asc/.msg file display
routines (e.g. putmsg) will still display Ctrl-A/0x80+ codes just fine.

text and quoted text. Enabled with the "-utf8" command-line option or by
setting utf8_support=true in the [fseditor] section of modopts.ini.
When UTF-8 support is enabled, the corresponding SCFG toggle option
("Support UTF-8 Encoding") should also be set to "Yes".
This is still a work-in-progress and UTF-8 character input and inserting
ASCII chars on lines that contain UTF-8 is still problematic.

editors that do not support UTF-8 (all of them, currently).

(default: No).

- bstrlen() moved to sbbs_t, accepts an option pmode argument so it can account
  for UTF-8 encoded strings correctly
- JS console.strlen() now accepts an optional pmode argument (e.g. P_UTF8)
- Renamed sbbs_t::utf8_to_cp437 to sbbs_t::print_utf8_as_cp437
- Create/use msghdr_hfield() to perform UTF-8->CP437 conversions as needed for
  printing/copying UTF-8 encoded message header fields.
- Defined XTRN_UTF8 misc setting flag. If a message editor does *not* have this
  flag, it is assumed to *not* support UTF-8. Will likely use this for UTF-8
  doors as some point too (none known to exist, yet).

new Socket(true) // creates an IPv6 TCP socket
new Socket(SOCK_STREAM, true) // creates an IPv6 TCP socket
new Socket(SOCK_DGRAM, true) // creates an IPv6 UDP socket
new Socket("myprot", true) // creates an IPv6 TCP socket named "myprot"

support to the JS API.

success. Upon failure to resolve, resolve_ip() returns null.

exit), just log the error and continue processing. Reported by wkitty42.

- Don't ever try to unpack a 0-byte file.
- Don't log anything or try delete if the file is < 24 hours old.
- Try to delete the file if it's >= 24 hours old (and log a msg, INFO-level).

I plan to convert all these to wiki-syntax eventually anyway.

show_msghdr()