On Wed, May 01, 2002 at 10:09:11AM -0400, Jeff wrote: > Nick Glencross wrote: > > > > Has anyone given any thought to a gcc backend for generating parrot > > assembler? > > > > Even with a partial implementation in place, it would be presumably be > > possible to use much of core C, with the benefits of register > > allocation, optimiser etc. > > > > Obviously it wouldn't be able to use much of parrot's powerful string > > handling or PMCs though, as C cannot convey these concepts. Of course, > > these could probably be hacked in as pseudo-function calls. > > > > Any thoughts? Anyone tried? > > Hi, Nick. I think that question is covered in the Parrot FAQs. Try > <http://www.parrotcode.org/faq/#why aren't you using external tool or > library x> for more information.
I don't think licening issues should prevent any particular avenue being explored by anyone interested in it, so long as they understand the implications (in terms of what would/wouldn't be accepted into the Parrot distribution). The FAQ should probably say as much. I'm not sure what the licening issues would be in this case anyway. Being able to target any gcc suported language to parrot sure seems like a good idea to me. In theory at least. If only for random experimentaion and stress testing of parrot. Tim.
