| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
Hi andrew. 10-Nov-02 01:30:42, andrew clarke wrote to Scott Little ac> Wed 2002-11-06 09:16, Scott Little (3:712/848) wrote to andrew ac> clarke: ac>>> I couldn't find any ",T:" in my nodelist, so I think that's a ac>>> non-issue, unless I've misunderstood. >> I mean, rather than Txx use T:xx so it's easier to parse. ac> Well, firstly, that's something you should really take up with ac> whoever wants to modify FTS-5001, ie. not me. Also Tyz is the ac> format people are using in my current nodelist so presumably they ac> aren't going see any reason to change. As for actually parsing ac> it, it's seems simple enough to me - if the nodelist flag begins ac> in T and contains non-alphabetic characters or isn't 3 characters ac> long then it must be something else. But if it is a valid Tyz ac> string then you just need a lookup table lookup table? it's a pretty simple formula for each character, for each character; this many minutes after midnight: 30 * ((((c-'A') * 2) & 62)+((c-'A') & 32)/32) That's C but it's basically the same in pascal etc. Anyhow works ok how it is, it's just ugly. other flags have the name separated from the data. hmmm, I guess if the flags are defined (in the parser) to include the separator as part of the flag it could simplify programming without making Txx a special case. -=> Bye <=- ---* Origin: Who's on first? (3:640/531.42) SEEN-BY: 120/544 123/500 132/500 400/300 490/33 633/104 260 262 267 270 284 SEEN-BY: 633/285 634/383 640/531 954 1674 690/682 712/610 848 713/615 771/4020 SEEN-BY: 774/605 800/1 2432/200 @PATH: 640/531 954 774/605 633/260 285 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™.