Re: Re: Re: Re: message from Parrot PieThon developer
"Mark Hahn" <[email protected]>
| Newsgroups | gmane.comp.lang.prothon.user |
|---|---|
| Message-ID | <008301c467cf$ba53ecd0$0d01a8c0@MarkVaio> |
Lenard Lindstrom wrote: > On Sun, 11 Jul 2004 11:42:30 -0700 Mark Hahn <[email protected]> wrote: > >> >> The big problem is that switching to Parrot is a one-way decision >> for me. I don't have the luxury of doing it as a research project >> on the side. I either stick with APR or jump to Parrot and live or >> die with Parrot. If I jump to Parrot and it takes years to finish >> or never finishes, then Prothon is doomed. I can't take that chance. >> > I finally remembered I could read the Parrot documentation using > perldoc. I have since found the assembly language description. There > is a lot of stuff that is irrelevant to Prothon. And it is not clear > if Parrot's PMC object handling is right for Prothon. It is geared > towards object-oriented systems. It would also turn every object byte > code operation into a function call. And I do not know how it would > handle op_ / rop_ combinations (Prothon does support rop_'s, right?). Yes. > And the Python benchmark code written for Parrot avoids many Python > features. Moving to Parrot would certainly be a risk. You are wise in > sticking with your own interpreter. A Parrot version can always come > later. > > Lenard Lindstrom > <[email protected]> > > > _______________________________________________ > Prothon-user mailing list > [email protected] > http://lists.prothon.org/mailman/listinfo/prothon-user