ERROR-level messages with error number, upon failure and debug-level message
upon success.

To hopefully help Deon get to the bottom of his SBBSecho echomail notification
issue.

We can't just memset() it.

Everyone gets an icon!

There's six pixels at the bottom that aren't part of text, and three
pixels on the right.

Don't touch the vmem when those pixels are updated... vmem can't
update them.

Should fix assertion in Abdul's Armor in RIP mode reported by DigitalMan
on IRC.

This should speed up loading the winnners list (e.g. when the syncdata msgbase
has a lot of messages) and scores won't be lost if the msgbase is purged.
Issue reported by Deuce (nix.synchro.net).

Bump version to 3.10.

Apparently, whatever was making this not link before has been fixed,
and so this workaround was breaking it.

Some scripts (e.g. addfiles.js) depend on the previous (undocumented) behavior
for some methods, e.g. lfexpand(undefined) would return undefined.

So for global functions that are expected to return a modified version of the
value passed (usually a string), return null or undefined when passed null or
undefined. Backward compatibility is more important than consistency in this
case. :-(

Fixes assertion/crash in 91-column mode (used in LORD intro screens)

EGA 80x43 has an extra six pixels at the bottom that are not part
of the text area.  When scrolling the botmap buffer, be sure to not
update this area.

Also, fix some screen invalidation bits when setting pixels.

This should fix ticket 180.

A high number of RIP commands use setpixel(), and it was updated
to scan the whole vmem for changes on each call.  Now we just extract
the part that is relevant and only update the one cell if needed.

This also adds parameter validation to bitmap_setpixel() which can
prevent some memory corruption and crashes.

... before the more ambiguous base filename check.

e.g. if you run 'jsexec /path/to/test.js' and get separate set of settings
from running 'jsexec test.js' depending on which sections you have added to
your jsexec.ini file.

And tests to insure the expected behavior

For those who want to force JPEG XL off, and don't use CMake

Disable it in jsdoor

Also, give test suites different names.

The behaviour is unreliable in Spidermonkey 1.8.5, and the behaviour
will change based on JS options.

If this file contains valid JS code that returns a true value, the
directory is skipped.

That just means we can't do parallel, not that we can't do JPEG XL

It wasn't in v0.6.x, which is packaged by Haiku.

This is really an error condition, so like the jsdocs say:
return undefined upon error

This how read(0) worked in sbbs, but not jsexec before that last commit,
so now just make readln and read work like that in both sbbs and jsexec.

Many global functions now throw an exception when null or undefined is passed
as a required parameter where null or undefined makes no sense.
e.g. "Argument #1 is an unexpected 'null' or 'undefined' value"
Example exception: is-a/has-a type functions will still return false when
passed null or undefined.

Changed global function return types:
- write() now always returns undefined
- printf() always returns a string, never undefined or garbage string
- prompt() returns null (not undefined) upon no input (as documented)

sbbs works more like jsexec:
- read(0) now returns an empty string instead of undefined
- readln(0) no longer waits for enter

jsexec works more like sbbs:
- add missing write_raw() global function, alias for write()

Include expected number of argment in "Insufficient Arguments" exception
message.

Update JSDOCS for some global methods:
- file_chmod returns boolean, not number
- flags_str requires a minimum of one argument

New tests to validate expected exceptions and return types based on usage.

Updated TS4S so we can build with -t while issue #777 is ongoing.

Ran `npm audit fix` to address a security issue in some dependency
of the build system. Perhaps this will silence the alert GitHub
sent to DM; I'm not sure what that was.

Don't use chdir(), just use js.exec_dir instead (e.g. for location of test.crt)

Use console instead of stdout when stdout isn't defined.

Log the file and line number of an an exception in a nested test when it
happens.