Ok...I would use PIR. But another question...if I target parrot by generating a PIR from my code generator...that means for users of my compiler to be able to run the PIR code that would be invisibly generated by my code generator it means a Parrot VM must run on the user machine ? (1)
If yes to above...then how do I package the parrot VM along with my compiler so that a end-user of my compiler that installs my compiler on his machine would automatically have parrot install as well ? (2) And when my compiler needs to invoke the parrot machine to execute the PIR code generated by my compiler...would i simply call parrot.exe like i do from the command line ? (3) Does parrot support creating GUI widgets ? (4) I would kindly look foreward to your responses to the questions above. thanks kunle On Sun, Nov 14, 2010 at 8:59 PM, Andrew Whitworth <[email protected]> wrote: > I agree with NotFound on this. PIR is definitely the best choice from > those above. > > The documentation paragraph that you mention is highly misleading and > needs to be updated. Which page did you see it on? > > PASM is not really usable right now and has not been in some time. > PAST is an intermediate step in some compilers that currently is used > to generate PIR. The only real choice from that list is PIR. > > We are working on libraries and routines to automatically generate > Parrot bytecode instead of needing to generate an intermediate form > first. Once we have those tools available and ready for production > use, I would recommend them instead. For now, use PIR. If your system > has pluggable back-ends, that would be the best because eventually you > will be able to replace the PIR backend with something better. > > --Andrew Whitworth > > > > On Sun, Nov 14, 2010 at 2:43 PM, NotFound <[email protected]> wrote: >> Hello >> >>> My Questions : >>> 1) if i have to write the front-end of my compiler in >>> c/c++...which of the above parrot code variants(PIR,PASM,PAST) would >>> be best for me to taget ? >> >> The easier way is to target PIR. PIR is a sort of powerful assembler >> and PASM is more like the assembler listed by a debugger. PAST is >> intended (for a now, at least) to parrot front-ends, not for external >> ones. >> >> You can look at winxed stage 0 for an example of a compiler writen in >> C++ that targets PIR. http://winxed.org/ >> >> -- >> Salu2 >> _______________________________________________ >> Parrot-users mailing list >> [email protected] >> http://lists.parrot.org/mailman/listinfo/parrot-users >> > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
