Re: RE: Prothon on CPython intrepreter? [PROTHON]
Mark Hahn <[email protected]> Wed, 11 Aug 2004 11:45:53 -0700
| Newsgroups | gmane.comp.lang.prothon.user |
|---|---|
| Organization | Hahn Creative Applications |
| Message-ID | <[email protected]> |
On Wed, 11 Aug 2004 08:49:30 +0100 (BST), Mukhsein Johari wrote: > --- Mark Hahn <[email protected]> wrote: >> >> In case I didn't make it clear in the previous >> message, I'm talking about >> implementing a C-based Prothon interpreter >> (CProthon) by heavily modifying >> the C-based Python interpreter (CPython). This > > Mark, could you give some reasons as to *why* you want > to do this? IMHO, the cool ideas you were thinking > about (stackless etc) wrt. the prothon interpreter are > much more interesting. It will still be Prothon. I will be using prototypes, stackless, unicode strings, flexible scoping, all the Python fixes, etc. with this scheme also. I will be losing native threads and object locking. >> The Prothon language itself would not be compatible >> with the Python language >> so any part of the library written in Python would >> need to be manually >> ported. There would be a utility to textually >> replace Python constructs >> with Prothon constructs but this would only >> accomplish 90% of the porting. > > This could still be done *without* utilizing the > python interpreter. Textual replacement and manual > greps...we don't need the python interpreter for that, > do we? > > Considering that we *still* have to port the vast > python libs anyway... what are hoping to gain? I'm > thinking that as more people use prothon, many will > port their favourite python modules anyway. No, we don't have to port the Python libs. All the interesting libs are C extensions and they will work. The small bits that are coded in Python code will be easy to port manually.