src/sbbs3 js_global.c 1.405 1.406
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv20353

Modified Files:
js_global.c
Log Message:
When a server does a background load, this line would be logged to the terminal server (uck). Needs an lputs() callback or similar.


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

src/sbbs3 js_global.c 1.406 1.407
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv8881

Modified Files:
js_global.c
Log Message:
Add global socket_errno_str property for cross-platform description of last socket-related error.


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

src/sbbs3 js_global.c 1.408 1.409
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/home/rswindell/sbbs/src/sbbs3

Modified Files:
js_global.c
Log Message:
Bug-fix: global socket_errno_str property returned numeric value (not string).



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

https://gitlab.synchro.net/sbbs/sbbs/-/commit/7c12761d51ebc0a33482d62f
Modified Files:
src/sbbs3/js_global.c
Log Message:
Add global methods: strerror() and socket_strerror()

If you have a stored errno value (or Socket.error), these are how you convert that number to an error description.

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

https://gitlab.synchro.net/main/sbbs/-/commit/d083d463917d83c4e0e3fd02
Modified Files:
src/sbbs3/js_global.c
Log Message:
Don't log an error when JS resolve_ip() fails

e.g. don't log the error "term !ERROR resolve_ip example.com failed with error -2", just let the script deal with the failure and log an error if it wishes.

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

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

https://gitlab.synchro.net/main/sbbs/-/commit/99b8b33b963484f94dc6b206
Modified Files:
src/sbbs3/js_global.c
Log Message:
Update JSDOC descriptions for md5_calc() and sha1_calc()

to clarify how many hex digits will be included in the returned (hex) strings

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