-----BEGIN PGP SIGNED MESSAGE----- At 07:28 +1000 on 13/10/97, Chris Nandor wrote: >At 16.47 10/12/97, Mark F. Murphy wrote: >>Well... I was hoping I didn't have to translate the files first. I was >>kinda hoping MacPerl would work with either transparently. > >Nope. This isn't a good idea. What if you wanted embedded \012 characters in your MacPerl script? In most cases I've worked with, there's no need to embed control codes at all. I either use "\0x0A" (or "\012" or "\0x0D" or "\014") for the special characters if I'm editing a binary-mode file, or I put special comments in for parseing purposes. Does anyone have other reasons for embedding control codes? As far as automatic translation goes, I develop a script on my Mac, then FTP it to the Linux host in ASCII mode. This works wonderfully. If there is a need, I can do "last minute" changes using my Linux text editor (my preference is Pico, but I know some diehards who use vi), then transfer it back to the Mac, once again in ASCII mode. Regards, Alex Satrapa -----BEGIN PGP SIGNATURE----- Version: 2.6.2, by FileCrypt 1.0 iQCVAwUBNEFfqGFCmlEesL8FAQFttwP/ZevA56WP8+amDVmUghoDuQ+rK3A5mB58 86A6kNk6Jy43VR1AeK0esdBwWbwzU58M+dH3sOTQYeEEw/vNAvfEmef5T9yBFzsi p7hFXAZcDxUGt69W75iRcUIYNR3394G+nc4yO58Q1ZwxRTJrTIUwNMSoRwPVcM5r ypZJ1PmQaGY= =Iqne -----END PGP SIGNATURE----- finger packrat@ucnet.canberra.edu.au for pgp public key. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch