Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    PASCAL    |    Pascal programming language discussions    |    592 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 284 of 592    |
|    mark lewis to Tony Langdon    |
|    Active or dead?    |
|    02 Nov 16 10:36:52    |
      02 Nov 16 16:42, you wrote to me:               ml>> if the tool is written in freepascal, it will likely handle the EOL        ml>> just fine... i have a project here that is written in FPC and it        ml>> works fine on native OS/2 and winwhatever... i copied the code over        ml>> to a linux box and pulled the data files in and it read them just        ml>> fine with no dancing about with EOLs... the data files come in in        ml>> zips and are unzipped with no special options give... especially not        ml>> the one to change EOLs...               TL> Even when the file is from a foreign OS? (e.g. Windows text file on        TL> Linuxx and vicew versa).              AFAIK, yes... i have no clue what OS the data files my project works with are       created on or what kind of transfers and conversions may happen before the       data is zipped... we use a script that pulls the zips from the remote       server(s) and unzips it... then my project takes existing data in locally       processed text files and loads in the new data from the remote server... it       hasn't cared about EOLs on any systems i've run the project on... each one       pulls the data archives from the remote server(s) and off we go to the races...              [time passes]              i just took a look and i have data files with 0xOa and 0x0d0a EOLs... they are       all read with no problem... output files from my project take the EOL for the       system it is running on so a 999 line output file on the linux box will be 999       bytes smaller than the exact same output file created on a winwhatever or OS/2       box... the difference being, of course, that 0x0d is not there...              now, if one must have the same EOL, that's easy enough to do... IIRC, there's       one system variable that you can ""override"" to make it use 0x0d0a for EOL on       all systems... or you can go for 0x0a on all or even 0x0a0d (older mac eol) if       you desire...              FPC is very flexible when it comes to plain ASCII text files using the       traditional readln and writeln routines... now, if you want to use that UTF-8       mess, it is a whole other story...                     FWIW: my project is a TLE processor... if anyone knows what a TLE is, they       will have an idea of what my project does ;)              )\/(ark              Always Mount a Scratch Monkey       Do you manage your own servers? If you are not running an IDS/IPS yer doin' it       wrong...       ... Cat with a full-auto M-16: Terror of poodles everywhere!       ---        * Origin: (1:3634/12.73)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca