Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MAKENL_NG    |    MakeNL Next Generation.    |    1,725 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,237 of 1,725    |
|    Michiel van der Vlist to Andrew Leary    |
|    Trailing comma    |
|    30 Jun 14 15:20:31    |
      Hello Andrew,              When line ends with just the baud rate field as fo rexample in 2:280/127,       MakeNL addes a trailing comma when it is not there:              Pvt,127,Trapgate_Test,Brunssum,Frans_Lupschen,-Unpublished-,300,              It does not add a trailing comma, when the baud rate is not the last field.              FTS-5000 allows the trailing comma, but does not require it.               FTS> Any remaining fields from position eight (8) onward are flag        FTS> fields. Note there may or may not be a trailing comma after        FTS> Field 7 if there are no flags listed.              I think MAkeNl should not forcefully add a trailing comma. It should also not       remove it when it is present in the submitted segment. It should just pass it       "as is" in the case that field seven is the last field.              In Zone 2 we have the odd situation that the R28 segment that I edit does not       have the trailing comma. When I run it trough MakeNl, it adds the comma. I       submit it to the ZC, who runs it through a filter (ERRFLAGS) that removes the       trailing comma. It reports it as an error. And then the ZC's MakeNl puts the       comma back in....              We could make it an option, but just not touching the trailing comma would be       fine with me.                     Cheers, Michiel              --- GoldED+/W32-MINGW 1.1.5-b20110320        * Origin: http://www.vlist.eu (2:280/5555)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca