change.

items (regardless what the user has "access" to), while the _list arrays
continue to only contain items the current user has access to.
Script writers using the associative arrays can check the "index" property to
verify the user has access to the item in question (a value of -1 indicates the
item is not in one of the _list arrays because the user has no access).

xtrn_area...prog_list[].

per item, but not necessarily consecutive for all users).
Created _area.*.index properties for indexes into _list arrays (consecutive
for all users).

(whenever possible), for documentation purposes (jsdocs.js).

Checking more JS API return values for failure.

"max_bytes" value is insufficient for the number of configured items:
by defining dynamically created objects and arrays as properties of child
objects of the global object immediately after such objects are created,
they are "implicitly rooted", protecting them from (unexpected) garbage
collection. Now the initialization will simply fail with a nice "out of memory"
error. This was a long-standing bug that rarely occurred in the wild.

Added more property descriptions (for dynamic JS object model docs).
Fixed a few bugs exposed by jsdocs.js.
Using JS_NewNumberValue for full 32-bit integer support (bitfields mostly).

reasignment by script author accidentally using object name as local variable.

(associative array).

to scripts with no user logged in (e.g. fingerservice.js).