| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
Hi andrew. 05-Nov-02 11:20:48, andrew clarke wrote to Scott Little ac> Sat 2002-11-02 10:08, Scott Little (3:712/848) wrote to andrew clarke: >> While we're at it, can we standardise the Flags formatting too >> (FTS-5001)? Eg. rather than Txx T:xx, making it simpler to parse them >> generically. ac> I couldn't find any ",T:" in my nodelist, so I think that's a non-issue, ac> unless ac> I've misunderstood He's pushing to separate the data part from the identifier part. The way we have it there's over 2000 different Txy type flags possible by putting the colon in in the new format there's one T: that has a 2 character data field after it. otherwise you make T a special case when parsing the nodelist and speaciual cases are yucky and tend to cause problems in the future, personally I'd prefer to replace the Txy flag with TIME:xy or similar conversion software (to produce FTS5 nodelists) should be able to to that conversion. -=> Bye <=- ---* Origin: Save energy: be apathetic. (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™.