At 11:12 AM -0700 2000-12-09, Douglas P. McNutt wrote: >I don't think that answers the question. \n denotes the line end character >on the current machine. The problem is how to handle line ends in files >that originate in a different machine and are not "corrected" by the likes Yes, this is the problem addressed by the "end-to-end" argument. Even if FTP could magically distinguish text files from binary, it still can't translate files in compressed archives, for example. Reliable communication is ultimately the responsibility of the application endpoints, not the transport layer. >of ASCII mode ftp. What perl really needs is a option that asks <READ> to >honor any of the four possible combinations the way browsers, M$Word, and a >lot of other software does. It's not a new subject and it also affects the >input of foreign perl code to the MacPerl "compiler". Four? I know of CR, LF, and CR/LF. What's the fourth? Josh -- Joshua Juran Metamage Software Creations =) Tools for Wizards wanderer@metamage.com <http://www.metamage.com/> * Creation at the highest state of the art * # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org