rather than 0 (a number) when the current sub-board or directory is invalid
(e.g. no user logged in yet).

- this option has been a default option flag for 10 years
- this option was introduced *before* the RLogin password capability
- Synchronet now always expects the login-ID (alias) to be the 2nd string
received during RLogin connections (called 'server-user-name' in RFC 1282.
* Now storing the complete terminal type/speed string received during RLogin
connection in the bbs.rlogin_terminal property (sbbs_t.rlogin_term in C++).
* bbs.rlogin_gate() is over-hauled:
- arguments are: address, client-user-name, server-user-name, terminal, mode
- if existing JS module assumes this to be: address, server-user-name, password
  those scripts will need to be updated to reflect the correct argument order
- all arguments beyond the first are now optional
- the terminal string can now be passed-in
* Deprecated the telnet gateway option: TG_SENDPASS (the 'password' if desired
to be sent as the 'client-user-name' can be specified as an argument and this
option sent the password as the *second* RLogin string ('server-user-name'),
which was always wrong.
* sbbs_t::telnet() can now accept the terminal string as an optional argument.

avoid freeing NULL pointers when called without all the (optional) arguments.

or 'longs'. Amazing that no one noticed.

rev 1.140 - this is why Synchronet boards started displaying "PW:" instead of
"Password:" for the password prompt (see exec/login.js for details why).

added bbs.rlogin_gate method: bbs.rlogin(addr,user,pass,mode);
disable "raw input" mode for rlogin_gate connections. not sure why this is the fix or why it was the problem, but no side effects are noted at this time.

of the first message in the thread, or 0 if unknown (e.g. legacy message). When
a new message is created, the thread_id value of the message being replied-to
will be used, else if the new msg is not a reply, then the new message's number
will be the value used for the thread_id.
This "thread-id" feature (Deuce's idea) allows threads with a common parent to
remain logically grouped after the original messages in the thread have been
purged (though the original hiearchy will start to be lost).

(throws an "Error: Insufficient Arguments" exception) in js_global.c so
all JSNative functions call call it.

Also add a function which calls JS_GetContextPrivate and throws an exception
if it returns NULL.

Previously, when either of these happened, the function silently did
nothing.

will now (hopefully) throw an exception.

This exception is likely to be uniquely unhelpful right now... I'm sure I'll
have to add good messages there Real Soon.

resolve callbacks.

code.

Perviously, if the argument to a number of bbs.* functions was not a valid
number, Synchronet would silently ignore the parameter and treat it as though
it was not specified.

The new behaviour was to use the value as a number.  However, the old code
caused the exception triggered by an inability to convert the number to
be pending until after the return (the JS_Native didn't return JS_FALSE) so
a try/catch block aorund it would not catch the exception.

The new new behaviour is to throw the exception immediately so it can be
caught and handled correctly.

all exported functions and data types using a 32-bit time_t (time32_t).

Only js_ValueToStringBytes() still leaks.

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

User.compare_ars() method, e.g. it knows the BBS node's current system status
(e.g. temp sysop), but can only be used for the current user online.

argument.

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

some requests for clarification from Deuce.