https://gitlab.synchro.net/main/sbbs/-/commit/d5516d0fdfa0683f399a977b
Modified Files:
src/sbbs3/js_global.c
Log Message:
Global JS exit() function now sets 'exit_code' to 0 by default

Calling exit() causes JS_ExecuteScript() to return false (same return value
as if there's a syntax error) - so if we always set exit_code in exit()
(even when not passed a parameter) and then use that exit code if the property is defined, then we get the -1 return value from js_execfile() if the script
is terminated prematurely without using exit().

This fixes the issue introduced in the previous commit where scripts that
call exit() - without any parameters, were causing errors to be logged about scripts (e.g. timed events) returning -1.

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

https://gitlab.synchro.net/main/sbbs/-/commit/0f00cbea87ded29aa84e6847
Modified Files:
src/sbbs3/js_global.c
Log Message:
Fix multi-array version of socket_select() when using poll()

Previously, when multiple lists were passed, the "write" parameter
(which can't be changed) was applied to all sockets. This means
they would always all be poll()ed for read, then checked for the
appropriate flag (read/write/priority)... which effectively meant
that only the first (read) array would work.

---
ï¿­ Synchronet ï¿­ Vertrauen ï¿­ Home of Synchronet ï¿­ [vert/cvs/bbs].synchro.net