If memory serves me right, James Michael DuPont wrote: > > > Bah. That's "parrot -o foo.o foo.pmc" isn't it? > > > > And if we make C a parrot supported language we can even build parrot > > with parrot?
Hmmm... bootstrapping .... > 1. The gcc : I have %99 of the information about the function bodies of > parrot c source code in rdf/xml. That could be fed to parrot. That would only be part of the issue ... generating stuff out of RDF AST's is only half of our trouble ... In fact , I think it would be much easier if someone managed to convert RTL into Parrot (a gcc backend) ... It won't be a "hack" like egcs-jvm since Parrot is already a register machine and has pointer instructions already ... > 2. The pnet/C : there has been work done by Rhys to make a managed c > compiler for pnet. Gopal has been working on a parrot bytecode emitter > for Pnet. Well ... I haven't been "working" on parrot bytecode emitter ... It's just that we have a "pm_codegen.tc" treecc handler inside parrot which is stubbed up ... until I can do some kind of class generation for parrot, the C# AST cannot be used for anything useful. Also Dan was not so hot about having a C compiler for Parrot when he met Rhys on IRC... So I'm sticking to compiling C# to Parrot as an aim , and *maybe* Java as well ... Gopal -- The difference between insanity and genius is measured by success
