https://gitlab.synchro.net/main/sbbs/-/commit/4365aac62118b6e5a509f219
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Don't compile the .ini parsing stuff for JSDoor

This should fix the recent JSDoor build issue introduced.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/8f4425cba02558a1c2c31fca
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Enable JSOPTION_VAROBJFIX for JSDoor.

This option fixes the fact that the following two lines sometimes
place the variables in different scopes at the top-level of included
scripts:
var x = 1;
y = 2;

I plan to use this to experiment on if this is what's causing much
of the remaining scope chain weirdness... it certain explains some
things we've been seeing (and possibly even things like the METHODJIT
issues DigitalMan saw yesterday).

Enabling in sbbs/jsexec is a much bigger lift, but this change may
end up being all upside... the docs have suggested this option always
be set since it was originally introduced, and now that I understand
scopes better, it's pretty clear why that is.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/a64184e0046bdda67b3cdce1
Modified Files:
src/sbbs3/jsexec.c
Log Message:
JSDoor still needs the module name.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/aa4c080b13259eaa89016787
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Typos in help

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/3313031a70bb0b995e0006ea
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Don't fclose(errfp) if it's NULL.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/d49facc893a919fefcb8969d
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Flush console output stream after executing a script

Solves problem of status output lines being interleved with console
output (e.g. from print()) after executing a script.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/7b932f63e4f1d4275e55dfbf
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Only create/use a single run-time for use in JSexec, even when re-runnning

The '-l' (loop) option would cause the JS runtime to be destroyed and
recreated for each new execution of the script, which resulted in memory
leaks in Windows builds (see issue #672 for details). So instead, just
use a single JS runtime here when the -l option is used to prevent that
from happening, though truth be told, that's likely not a normal/common occurrence. Other apparent JS-related memory leaks (e.g. in the web
server) appear to be of a common concern.

Likely upgrading to a modern libmozjs would also fix this issue, but
we're far short of being able to do that right now.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/b53254b6bcc9d02aae63da2e
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Resolve full path to specified ctrl directory, before chdir

If a relative path to the ctrl directory is specified on the command-line
or in the SBBSCTRL environment variable, the loading of ctrl/*.ini would
fail after the changing of the working directory.

We should probably get replace all use of FULLPATH with _fullpath someday,
but for now, I just went with majority-rule.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/7d3b61d7f59fcdf32e739baf
Modified Files:
src/sbbs3/jsexec.c
Log Message:
PATH_MAX (not an MSVC thing) -> MAX_PATH

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/97fb3f1f463adc057fc05ea8
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Make Windows hack Windows-only

We need _CIOLIB_main on macOS... at least until the curses stuff works.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/1e48f1252859924638b52e96
Modified Files:
src/sbbs3/jsexec.c
Log Message:
Don't use the non-standard third parameter to main for enivronment

Use the standard `extern char **environ' instead.
Fixes an issue with macOS.

Also, check that env is not NULL in js_init.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net