RE: Prothon on CPython intrepreter? [PROTHON]
"Mark Hahn" <[email protected]> Sun, 15 Aug 2004 20:52:56 -0700
| Newsgroups | gmane.comp.lang.prothon.user,gmane.comp.python.devel |
|---|---|
| Message-ID | <000001c48344$847e6ff0$d801a8c0@MarkVaio> |
Paul Prescod wrote: =20 > Mark Hahn wrote: > > I think you are missing the point. You are explaining how to=20 > > implement Prothon with the CPython interpreter. I know how=20 > to do that. > >=20 > > What I was questioning was your idea to make Prothon upwards=20 > > compatible with Python. I don't see how that could be done. My=20 > > changes to Python would break existing Python code. >=20 > It is probably not relevant anymore as it looks like you are leaning=20 > towards .NET but: >=20 > Python would have one parser and Prothon would have another. The two=20 > would share a VM, just as two parsers can run on the same VM on .NET. >=20 > 90% of bytecodes would be shared between Python and Prothon but there=20 > might be a few that would be unique to each. After giving this much thought, I finally have a handle on the = situation. I can go with Cpython or .Net, but if I go with Cpython I am taking on = both the task of making a new Python VM that is compatible with multiple languages and the task of implementing Prothon on top of that new VM. Now if we can get others interested in helping with the Python VM = project, I might take that on. I certainly don't want to do all that by myself = though. I have been studying what .Net has done for multiple language support = the last few days and I have a good understanding of it now. I am quite impressed and it has given me ideas for what could be done with the = Python VM. I feel that doing .Net will give me lots of practical experience with porting a language. It will also be the cleanest, quickest = implementation of Prothon. Jim has offered good support from Microsoft. After .Net I will be in a good position to do any of PyPy, CPython, CProthon, or who knows what. After thinking about CPython so much for a few days, I'm thinking that = maybe it would be the right way to do CProthon. In other words, even if I = write a VM from scratch it should probably be Python compatible. You aren't regretting talking me into to doing .Net, are you?