On Sun, Oct 12, 1997 at 09:26:32PM -0400, Richard Rathe wrote: } } I still find it amazing that Perl is non-portable BY DESIGN!?! The concept } of end-of-line is so universal, I fail to understand why this problem isn't } "taken care of" behind the scenes... It is. Use native text, and everything works. Use non-native text, and nothing works. } } On 10/12/97 Chris Nandor wrote: } } >Nope. This isn't a good idea. What if you wanted embedded \012 characters } >in your MacPerl script? } } ... But doesn't the same problem crop up after you've done the conversion } with a text editor? I'd much rather work around the exceptions (the need } for weird characters in my files) than the rule (MacPerl blind to every } UNIX script in existence!) Another example is the directory delimiter. What } harm would be done if MacPerl automatically changed '/' to ':' and back } again when it works on directories and files? And what would you do with a file named "Macintosh HD:Logs:10/11/97"? } } Don't get me wrong, I like Perl and I think MacPerl is a godsend. This is a } question, not a flame. <smile> } } Thanks, RR } } PS to Matthias: Maybe the MacPerl editor could prompt the user and then } convert text files brought over from UNIX and that 'other' OS.... } } __________________________________________________________________________ } Richard Rathe, MD mailto:rrathe@dean.med.ufl.edu } University of Florida http://www.med.ufl.edu/medinfo/ } } } } ***** Want to unsubscribe from this list? } ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch -- -------- Paul J. Schinder NASA Goddard Space Flight Center schinder@leprss.gsfc.nasa.gov ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch