If a function exists in `func_list` with a value of 0, then it is expected to be callable with `null` or `undefined` as the first argument //without// throwing an exception.
If a function exists in `noargs_required` then it is expected to be callable with **no** arguments without throwing an exception.
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
From Deuc¿@VERT to GitLab note in main/sbbs on Sat Jan 18 18:26:03 2025
How is that wrong? If the element value is 0, then a caller can call the function with a (single) null/undefined argument. If it's 1, they can't (it'll throw an exception).
Calling with a null/undefined argument is different than calling with no arguments.
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
From Deuc¿@VERT to GitLab note in main/sbbs on Sun Jan 19 10:28:23 2025
It translates to "Zero is the number of non-null/undefined args required." Which does not translate to "One is the number of null/undefined args allowed."
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
Who's Online
No nodes active
Recent Visitors
Genalb
Sun Jul 13 07:23:59 2025
from
Slc, Utah
via
Telnet
Genalb
Fri Jul 11 08:11:07 2025
from
Slc, Utah
via
Telnet
Genalb
Sun Jul 6 07:06:10 2025
from
Slc, Utah
via
Telnet
Chris Test
Sun Jul 6 01:52:08 2025
from
Dallas, Texas
via
HTTPS