I wondered why Crashmail shows an invalid month in the packet date:
Tossing 027deab2.pkt (3K) from 21:1/100.0 (04-???-19 05:01:05) / 4d
It turns out Mystic uses 1 to 12 instead of 0 to 11 for the month as specified
in FSC-39:
Hello Oli,
Another bug? Really??
I wondered why Crashmail shows an invalid month in the packet date:
Tossing 027deab2.pkt (3K) from 21:1/100.0 (04-???-19 05:01:05) /
4d
Probably because January IS the first month of the year. Also
probably why people born say on January 24 1990 don't consider
themselves born on 00/24/1990.
And why software uses a date structure that IS currently in use.
It turns out Mystic uses 1 to 12 instead of 0 to 11 for the month as
specified
in FSC-39:
You mean "proposed, but not currently in use"?
BTY, This is EOT for me for this pointless thread.
Hello Oli,
Another bug? Really??
I wondered why Crashmail shows an invalid month in the packet
date: Tossing 027deab2.pkt (3K) from 21:1/100.0 (04-???-19
05:01:05) / 4d
Probably because January IS the first month of the year. Also
probably why people born say on January 24 1990 don't consider
themselves born on 00/24/1990.
And why software uses a date structure that IS currently in use.
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 220:07:00 |
Calls: | 14,143 |
Calls today: | 1 |
Files: | 295 |
Messages: | 551,172 |