Re: [MacPerl] Embedded Control Chars (fwd)

[mark@cheers.jsc.nasa.gov (Mark Manning/Muniz Eng.)]

According to Chris Nandor:
> At 11.55 10/17/97, Mark F. Murphy wrote:
> >At 8:07 AM -0400 10/17/97, Chris Nandor 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 ...

I think he meant to equate the MacPerl programming
environment to the CodeWarrior programming environment.
Like if you opened a file in MacPerl from a Unix system
you'd get a single, VERY long, line.  While in CodeWarrior
you'd just get a program listing.

The real difference though is that MacPerl is an endeavor
by one individual who has put in hundreds of hours of time
to make this work for all of us whereas CodeWarrior employs
hundreds of individuals who are really just out to make
lots of money.  Of the two - CodeWarrior has the snazzier
interface but is one heck-of-a lot harder to use than what
this one person has created.  I know I am impressed.  And
yeah, it would be nice if MacPerl could read/write multiple
platform files automatically - but that's not what
MacPerl's outlook is.  (At least as far as I can tell.)
MacPerl's outlook is to provide a stable program which runs
Perl code that was written to be used on the Mac.  Perl
itself is moving towards encompassing multiple platforms.
But I'm sure there are many stumbling blocks along the way
which must be overcome.  And again, since this isn't a
commerical endeavor it goes at a slower pace.  But at least
we aren't getting all of the commerical superhype that goes
along with software releases.  :-)


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