I saw that the bbs.compiled_when property is a string that contains the
date when Synchronet was compiled. I noticed that it's in the following format: May 12 2013 05:02
Is it always in that format with month names in English, regardless of the system's region and language settings?
I saw that the bbs.compiled_when property is a string that contains
the date when Synchronet was compiled. I noticed that it's in the
following format: May 12 2013 05:02
Is it always in that format with month names in English, regardless of
the system's region and language settings?
Apparently, yes. I'm on European time and region, and I get the following with system.compiled_when, as your subject:
C:\sbbs\mods\testing\compiled_when.js compiled in 0.00 seconds
May 8 2013 05:02
I saw that the bbs.compiled_when property is a string that contains the date when Synchronet was compiled. I noticed that it's in the following format: May 12 2013 05:02
Is it always in that format with month names in English, regardless of the system's region and language settings?
Hi DM,
I saw that the bbs.compiled_when property is a string that contains the
date when Synchronet was compiled. I noticed that it's in the following format: May 12 2013 05:02
Is it always in that format with month names in English, regardless of the system's region and language settings?
Re: system.compiled_when property
By: Nightfox to Digital Man on Thu May 16 2013 07:16 pm
Hi DM,
I saw that the bbs.compiled_when property is a string that contains the date when Synchronet was compiled. I noticed that it's in the following format: May 12 2013 05:02
Is it always in that format with month names in English, regardless of the system's region and language settings?
Yes. It's a build-time string and the C standard dictates the format.
Now, this is the date/time the executable was built, it does not tell you that it's "v3.16a" for example. You could build v3.15b today and the compiled_when property would contain today's date, but the version of the source would still be an older one.
Now, this is the date/time the executable was built, it does not tell you that it's "v3.16a" for example. You could build v3.15b today and the compiled_when property would contain today's date, but the version of the source would still be an older one.
Rather than basing your decision to use bbs.msg_number on the build date, why not check to see if it's non-zero? A zero message number is never valid. Just fall back to the previous behavior if the message number is zero.
Ah, I suppose I could do that. I didn't know 0 would be an invalid message number.
Rather than basing your decision to use bbs.msg_number on the build date, why not check to see if it's non-zero? A zero message number is never valid. Just fall back to the previous behavior if the message number is zero.
Re: system.compiled_when property
By: Nightfox to Digital Man on Mon May 20 2013 19:57:39
Ah, I suppose I could do that. I didn't know 0 would be an invalid message number.
Looking back at the related messages, you did say bbs.msg_number is
1-based. I think it's a better option to check for that rather than checking the version and build date of Synchronet.
Looking back at the related messages, you did say bbs.msg_number is
1-based. I think it's a better option to check for that rather than
checking the version and build date of Synchronet.
I agree.
Sysop: | Clippy |
---|---|
Location: | Houston, TX |
Users: | 4 |
Nodes: | 4 (0 / 4) |
Uptime: | 215:29:36 |
Calls: | 1 |
Files: | 11 |
Messages: | 38,209 |