| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | human-readable nodelist format |
Sun 2002-11-10 10:44, Scott Little (3:712/848) wrote to andrew clarke:
ac>> I can't decide whether you're saying it's too difficult to parse or
ac>> not.
> Fully specifying the address for each node bothers me, esp. in
> conjunction with the Uplink field.
Why?
> * Initial version. Currently the Uplink field in the human-readable
> * nodelist is ignored by rnlcvt. Which assumes the input file is
> * already in hierarchical order.
> A _correct_ implementation will be more complex unnecessarily in the
> name of human readability.
Not really. But keep in mind that rnlcvt's aim was just to check the
valididty of nlcvt's output.
> Much easier to extract a human readable list from a strict format
> than the other way around.
True. But still pretty simple.
-- mail{at}ozzmosis.com
--- Msged/NT 6.1.1
* Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267)SEEN-BY: 633/270 @PATH: 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™.