Re: [MacPerl] Embedded Control Chars

[pudge@pobox.com (Chris Nandor)]

At 19.50 10/17/97, Mark F. Murphy wrote:
>The issue is should a Mac version of the product be up to par with other
>Mac products.  In no way am I talling the developer of MacPerl what to
>do... however, I am mentioning what would be a nice feature.
>
>I kinda just expected my existing Perl scripts to work straight away
>without any conversion with BBEdit (which is what I use to write *all* my
>scripts for the other platforms).  I thought I could just use the Unix
>based scripts and MacPerl would do the right thing.  It doesn't.

Just one more bit of fuel to the fire: Unix perl cannot read Mac files, either.  :-)

At 19.40 10/17/97, Mark F. Murphy wrote:
>>>>Remember, though, that this is not a Perl-specific problem.  All languages
>>>>would have this problem.
>>>
>>>No.
>>>
>>>I can read C and C++ source files in CodeWarrior no matter what the EOL is
>>>(Mac, Unix, DOS).
>>
>>That has nothing to do with the programming language ...
>
>It does when we are talking *source*.... and I'm talking source.

At 19.40 10/17/97, Mark F. Murphy wrote:
>With C/C++ I do not have to keep different sources of the code in different
>text formats... at least not in CodeWarrior.  Codewarrior "does the right
>thing" as a good chunk of Mac programs do.  The user doesn't have to care
>whether the file came from Unix or DOS.

My point is that it is not the LANGUAGE, but the particular editor.  The C/C++ language has this problem.  CodeWarrior must convert the line endings before it can be passed to the compiler.  So yes, all languages have this problem.

--
Chris Nandor               pudge@pobox.com           http://pudge.net/
%PGPKey=('B76E72AD',[1024,'0824 090B CE73 CA10  1FF7 7F13 8180 B6B6'])
#==                    MacPerl: Power and Ease                     ==#
#==    Publishing Date: Early 1998. http://www.ptf.com/macperl/    ==#



***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch