module. This is a reversal of the revision 1.102 commit (Jan-2-2016), but only
for Baja (JS is left with the new behavior). As the commit message said
"We'll see", and what we saw was that the yesnobar.bin and noyesbar.bin
long-standing Baja modules no longer returned "No" when the user hit Ctrl-C.
So at least for now, we have different behavior with regards to the console
abort (ctrl-C) flag between JS and Baja. :-/

blowing up unexpectedly because of load() or a global hotkey event.

This solves the problem of a JS-external program (e.g. SyncWX) being aborted
at a pause prompt with Ctrl-C or Q and that abort status propagating back to
the external program's menu. If there is a module which needs to propagate
the console-abort status up to the parent(s), then this could introduce a
problem. We'll see.

Don't report a JavaScript warning ("Disconnected") until the OperationCallback
has been executed 10 times with the user offline. This gives the executing
script ample time to recognize the disconnected state and exit gracefully.
Script that do not check/notice that the user has disconnected will still be
auto-terminated (by default) and this warning will still be logged in those
cases. The value 10 was picked at random and appears to work fine.

New Features:
- Multiple bindings for each service
  Use comma-separated interfaces on Interface= lines in the ini file.
  Default is now "0.0.0.0,::"
- IPv6 support
- TLS support for the webserver and (non-static) services
  New TLS option in services.ini (ie: Options=TLS)
- Decrease LEN_SCAN_CMD to 35 chars, increase the CID field to 45 chars,
  and rename the MAIL_CMD string to IPADDR.  I think this frees up the
  note field for SysOp use.

scripts global scope (as opposed to js.global which is the instance global
scope), and having exit() define exit_code in js.scope instead of js.global.

This also sets exit_code in js.scope to null when preparing to execute a new
script.  If a new script starts in the same scope as an old one, the old
exit_code value will be destroyed.

This should only impact scripts where js.global != js.scope (bbs.exec()ed,
and mailsrvr)

calling any JSAPI functions.

has its own functional "too much recursion" detection.
Replaced "branch callback" stuff with "operational callback".
JavaScriptBranchLimit has been replaced with JavaScriptTimeLimit
(default value: 24 hours)

      on the floor of Deuce's computer room
Cyan: Rob's on his way
* Deuce throws his coffee on it.

Last commit before stuff starts to break.

are now executed with the node's global object as the scope of the script.

executed via exec_bin() - this had the side-effect of causing background loaded
threads to terminate when the script terminated (rather than when the node
context was destroyed) and also caused the node context to be unused
(for mcmlxxix).

Updated copyright dates.

make system.matchuserdata return an array of all matches if match_all==true, starting at usernumber if specified. (userdatdupe now takes an additional paremeter)

(potentially) non-blank for external JS modules configured in SCFG->External
Programs, as well as those executed from jsexec. If the startup_dir is
specified in SCFG and no path is given for the .js file, it will look in the
startup_dir first. js.startup_dir will be an empty string for all other cases
(currently).

is most likely a memory hog slowdown on everyone elses system, but it works
great for me and is fast and easy!

EX_STDOUT, defining EX_STDIO (to be both STDIN and STDOUT), adding XTRN_CONIO
and EX_CONIO (for future cioxtrn/doorway mode on Windows), change IO_INTS to
XTRN_STDIO

inserting (long) typedefs to prevent warnings, but in the case of the JS File()
class, actually supporting file lengths > 32-bit.

as single argument (strip quotes too?).

via sbbs_t::js_execfile() (e.g. executed via "?modname").

Don't prompt for "delete mail from everyone" when there is only one e-mail
waiting for the user.
Use some existing text.dat entries (some old and some recently added) where
identical static strings were still being used for no apparent reason.
Added several text.dat entries for the QWK settings menu, node status, and
some other single-line messages (replacing static strings).

created:
js.exec_path - full path and filename of file executed
js.exec_dir - directory of executed file
js.exec_file - filename executed (with no path)

Added HOST and IP keywords to allow restricted access/privileges to/for
specific remote hostnames or IP addresses (wildcards allowed).
All string-argument type ARS keywords (e.g. SHELL, PROT, etc.) now support .can
style wildcards.
The current remote client is now used for protocol, host, and IP ARS checking,
when available, so this requires passing the client pointer around (which
explains why so many files are touched by this change) and takes care of a
long standing to-do item (the user's 'modem' value was used for the PROT
value checking, which was not always correct).

js_EvalOnExit(). Call JS_ReportPendingException after calling js_EvalOnExit().

While you can't run with a missing text.dat yet, you should be able
to run with a zero-byte one.

bugs.

mods/*.js
exec/*.js
mods/*.bin
exec/*.bin

to:
mods/*.js
mods/*.bin
exec/*.js
exec/*.bin

at Hax0r's request.

(again, store an index into a DIR* array, rather than the pointer itself, into
the user's variable).