At 2:43 PM -0700 on 7/11/99, Alain Farmer wrote:
>Alain : So Perl is an option, after all? Do you remember the
>discussions we had several months ago concerning the pros and cons of
>programming with Perl versus programming with C/C++ ? I was promoting
>the Perl option earnestly but I was drowned out by the chorus for
>C/C++. I�m not upset about it at all. I�m just bemused by the fact that
>Perl is re-surfacing now. For the record, I welcome Perl as a
>programming language for OC, because I am sufficiently familiar with
>Perl that I could participate in the coding, while now I am limited to
>the collaborative aspects. No problem here either, though. I am mainly
>in it for the collaborative aspects. But, in addition to coding, the
>use of Perl would undoubtedly help me better understand what is going
>on and, thus, help me provide the group with better support for our
>collaboration.
Alain, I think you've misunderstood. We are talking about user perl itself.
We'd be changing the perl source code, which is in C. We would not be
writing in Perl.
>
>Alain : Perl has a huge following. My guess is that there is much more
>stuff coded in Perl than in Python.
Probably.
>
>Anthony : An egcs frontend would be nice while we're at it :)
>
>Alain : What is a �egcs frontend�? Is it Perl or Python or C?
egcs is a compiler. It compiles C, C++, Objective C, Pascal, and Fortran.
And maybe some others. If we added an OpenTalk frontend, it would compile
OpenTalk.
>Uli : I have a feeling that Hypercard is much more structured than we
>think...
I'd have to look at some Perl sources before saying what the chance are of
ever compelting such an undertaking as fitting a new language to them.