Hello Doriano, I have to excuse me - it was never my intention to insult your, as it seems deeper going feelings, regarding this particular 2 Bytes :-D
Ofcourse you are right - they are (and will be in the future also) still in use... But here is the point where I do not agree with you: I do not know how old are you... My first "date" with CR&LF was on my very expensive (>4000 USD) Apple ][ with the huge ammount of 48 KB RAM, 16 KB ROM, 144 KB Floppy Disk and rare extension - Video Card allowing me to work with 80x25 chars instead of the usual 40x25 ... Not to mention the extraordinary calculation power based on the 1 MHz 6502 CPU ;-). So please excuse when I am calling this "stone age", but my very simple mobile phone laying in my pocket offers 2 GB of storing capacity on volume that the old Apple used to store about 16KB and about 300 MHz RISC based power... It was not a try to reduce the meaning and importance of those command chars - but simply to show how long they are in use... Very best regards And one more time excuse my lack of respect Emil Tchekov -----Ursprungliche Nachricht----- Von: Doriano Blengino [mailto:doriano.bleng...@fastwebnet.it] Gesendet: Dienstag, 17. Februar 2009 23:15 An: mailing list for gambas users Betreff: Re: [Gambas-user] Help with some parsing Emil Tchekov ha scritto: > CHR$(10) & CHR$(13) - carriage return & line feed > Those are special "command" character from the "stone age" of the informatic > used to go to the next line (add new line) - was needed in the times where a > martix printer with ink ribbon the single output device of the computer > was.... > Pardon me to point out. I disagree, chr$(13) is CR; chr$(10) is LF. While it is true they are an old standard, saying they are "from the stone age" is not fair. HTTP protocol relies on CR-LF, and you must admit that HTTP protocol is well alive - not a "stone age" standard. The fact CR-LF is so old is a proof of its power. Moreover, text files are the most expressive and versatile form of digital data. Html, Xml, Svg, Postscript, PDF, are all in wide use and are based on ASCII, and so they contain CR-LF sequences. The fact Unix/Linux uses a single LF instead of a CR-LF is pretty marginal - it was simply a design choice. A windows HTTP server can take text files from disk and serve them verbatim, while a Unix HTTP server has to translate them (to add the missing CR). Anyway, the concept is the same. Most programs today can cope perfectly well with this two standars. In the end, the only thing I wanted to say is that CR and LF are far more than what you depicted, and they are still needed. Regards, -- Doriano Blengino "Listen twice before you speak. This is why we have two ears, but only one mouth." ---------------------------------------------------------------------------- -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user