Section One BBS

Welcome, Guest.


Subject: bbs.atcodes() Date: Sat Apr 30 2022 12:08 pm
From: Digital Man To: deon

  Re: bbs.atcodes()
  By: deon to Digital Man on Sat Apr 30 2022 10:17 pm

 > Hey DM,
 >
 > I've been playing with bbs.atcodes(), and I've noticed the following:
 >
 > synchronet: term Node 1 <X> Replacing [@DATETIME-L15@] with [Sat Apr 30
 > 2022] synchronet: term Node 1 <X> Replacing [@TIME-L8@] with [09:42 pm]
 >
 > synchronet: term Node 1 <X> Replacing [@DATETIME<pipe>L15@] with [null]
 > synchronet: term Node 1 <X> Replacing [@TIME<pipe>L8@] with [null]
 >
 > synchronet: term Node 1 <X> Replacing [@STATS.LTODAY-Z2@] with []
 > synchronet: term Node 1 <X> Replacing [@STATS.TTODAY-Z2@] with []
 >
 > synchronet: term Node 1 <X> Replacing [@STATS.LTODAY@] with [5]
 > synchronet: term Node 1 <X> Replacing [@STATS.TTODAY@] with [31]
 >
 > ie:
 >
 > If I use the pipe delimiter (I'm using the word <pipe> above only in this
 > message), I'm getting "null" instead of the value (it works with the dash
 > delimiter).

That's expected: bbs.atcode() does not support the formatting modifiers.

 > For the STATS<dot>XXX I'm getting nothing returned (regardless of whether I
 > use a dash or pipe delimiter), but I do get a return if I remove the
 > delimiter altogether.

Same answer: you can't use the format modifiers with bbs.atcode().

 > This is: JSexec v3.19c-Linux master/c0f42027d

Are you sure about that? JSexec doesn't instantiate the 'bbs' object, so that se
ems unlikely. But no matter, it's not an sbbs-version issue.

 > I think bbs.atcodes() is not working correct, am I on the wrong track?

Working as expected.
-- 
                                            digital man (rob)

Synchronet/BBS Terminology Definition #51:
MODEM = Modulator/Demodulator
Norco, CA WX: 77.2°F, 43.0% humidity, 10 mph E wind, 0.00 inches rain/24hrs

---
 ■ SynchronetVertrauen Home of Synchronet [vert/cvs/bbs].synchro.net

Previous Message       Next Message
In Reply To: bbs.atcodes() (deon)