Added xjs_eval(filename, str)
- notionally for evaluating XJS without immediate write
- if str, returns the evaluated script as a string
- if !str, returns the filename that the script was dumped to
- was a fun idea, but doesn't play well with other scripts
- best used with simple and self-contained xjs

<nelgin> However, dm should probably maintain it at the source.
<nelgin> DigitalMan, I've uploaded gtkuseredit_glade.c which also widens "Sex" to 5 chars
<nelgin> I've also uploaded my .glade file for comparison
<nelgin> and I've uploaded my convert perl script.
<DigitalMan> the sex/gender field is a single character
<nelgin> Yes, but it doesn't display properly unless I widen it to 5.
<DigitalMan> ah

Added libHasFiles(lib); returns true as soon as it encounters a
dir in a lib that has any files in it.
listLibraries() only returns libs that have populated dirs.

maybe that'll do something.

Same as while in list mode, offers download of message source or any
attachments.

Fix extraneous PAUSE prompt from Operator menu '?' command by using
P_NOCRLF mode argument to bbs.menu().

The password was (recently) limited to 8 chars, so that made sense.
The 24 character limit of the real name does not make sense and I can only
assume it was a typo.

- DATE: (alias: TIME:)
- BDATE:
- PWDATE:
- SINCE:
- LASTON:
- FIRSTON:
- LASTNEW:
- EXPDATE:

If the script encountered an exception, the bbs.sys_status would be
left in "no message" mode, meaning no node messages or telegrams would
be automatically displayed to the user.

Truncating. str is a pointer, so sizeof(str) is only 4 (or 8) bytes.

e.g. MM/DD/YY for drop files that assume that format, or either MM/DD/YY or
DD/MM/YY (depending on sysop preference) for backwards compatibility in
expanded @-codes, Guru chat keyword.

Fixed the birthdate check while logging on to work with new/all birthdate
formats.

i.e. from MM/DD/YY or DD/MM/YY to YYYYMMDD.

The C/C++ source still supports all 3 formats, so it's not terrible if the
birthdates aren't converted, but thing will be better if we do this ahead
of time and find all the remaining issues with the new format rather than
wait for new users (with the new format) to trickle in.

... and up to 200 years old (hey, I'm optimistic!)

Also, fixed get_date(), it returns 0 on success, but the success return logic was inverted:
it only returned 0 if the date was unchanged from the previous value.

Note:
It would be nice if this user editor prompted to save changes if changes have been made a new
user is selected (e.g. with the arrow buttons).

Would be nice to ignore exec/sbbs, addfiles, etc. too. Not yet seen a good way to do that.

These allow the easy reading or writing of these sub-field values of the
user.birthdate property. When migrating from the legacy formats (e.g. MM/DD/YY
or DD/MM/YY), it's required to write all 3 properties to get a correct
birthdate/age. Otherwise, "13/31/69" could become "19691/69" (for example)
which isn't going to parse correctly.

'i' is the return value of savemg(), used to determine success or failure
(and what kind of failure) - so we can't use that for the usernumber of
the recipient.

Support the old MM/DD/YY or DD/MM/YY format for reading. New users get the new format.

strcpy -> SAFECOPY
sprintf -> safe_snprintf or SAFEPRINTF2
strcat -> SAFECAT

Enabling this feature causes the node's temp directory to be cleared before
running the external program and causes the drop file(s) to be created-in and
read back from (when appropriate) the node's temp directory.

Creating drop files in a node's temp directory eliminates the possiblity of
an external program (e.g. door game) accidentally reading the wrong drop
file (e.g. wrong-cased name or a stale file of a different type).

Note: Synchronet/XSDK doors *always* read their drop file (xtrn.dat) from the
node directory, so don't try to use this option with those doors. Only doors
where you can configure the drop file path or specify on the command-line
(e.g. %g for the temp dir or %f for the fullpath of the drop file) should
potentially use this new feature.