| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | (1/3) Packet type 2, draft 990328 |
GE> 4 04H | Year | 2 GE> ----------------------- GE> 6 06H | Month | 2 GE> ----------------------- GE> 8 08H | Day | 2 GE> ----------------------- GE> 10 0AH | Hour | 2 GE> ----------------------- GE> 12 0CH | Minute | 2 GE> ----------------------- GE> 14 0EH | Second | 2 JH> IMHO this looks awful. Why can't this be done by simply using a JH> single integer UNIX style timestamp? Naturally it could have been done that way. Or in one of a number of other ways. Now, since the purpose of my work is to create an updated documentation of PKT type 2, which already has existed for many years, there's no alternative to describing it as it is. At least I would love to get rid of the unnatural representation of the month. ---* Origin: GET, Lidingo, Sweden, +46-8-7655670 (2:201/505.1) SEEN-BY: 201/505 633/267 270 @PATH: 201/505 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.