Re: [MacPerl] MacPerl future, was: README

[Axel Rose <rose@sj.com>]

>I think the contents of a MacPerl README can't really be nailed down until
>the distribution is about ready, since I don't think anyone yet knows what
>the next version is going to require in a README.  MacPerl might change in
>ways we don't know of yet.  We could draft one, but I'd just wait.

Hi Chris,

while you are speaking about future development ...

I have the sometimes doubtable pleasure to work with MacOS X Server.
I was really looking forward to test Perl programs on a Unix system.

MacOS X is shipped with two text editors: "TextEdit" and "Emacs 20.x".
Forget "TextEdit" - it can only save in RTF format.
When opening files with emacs you have to have Unix line breaks.
European extra characters aren't converted.
When copying with the MacOS X Finder equivalent from a Mac HFS+ partition
files are transferred with FTP (after interactively confirming the transfer).
Line breaks and extra characters are ignored.

Within a VT100 terminal (the only terminal emulation!) and a german
keyboard I can't type in special characters as '

It's pretty unusable as a Perl development platform for me.

I don't want to start a off-topic discussion here about Rhapsody
but think that MacPerl is unbeatable for still quite a while.


Sincerely


Axel

------------------------------------------------------------------
        Axel Rose, Springer & Jacoby Digital GmbH & Co. KG
                       mailto:rose@sj.com
pub PGP key 1024/A21CB825 E0E4 BC69 E001 96E9  2EFD 86CA 9CA1 AAC5
"... denn alles, was entsteht, ist wert, daß es zugrunde geht ..."

# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org