I could help you with the process_op_func.pl thing. Unless, you've already coded it yourself! :-).
Cheers, Vladimir Bogdanov. ps. have to figure how to get the WinCVS thing work... can't seem to be able to access cvs.perl.org. I've used the following set up: CVSROOT = :pserver:[EMAIL PROTECTED]:/home/perlcvs Authentication = passwd file on the remote host. any suggestion on how to make it work? -----Original Message----- From: Gibbs Tanton - tgibbs [mailto:[EMAIL PROTECTED]] Sent: Saturday, October 06, 2001 6:12 AM To: 'Simon Cozens '; '[EMAIL PROTECTED] ' Subject: RE: vtable.h for add we will end up with void add( PMC* self, PMC* left, PMC* right ); does this represent: self = left + right or some other ordering? -----Original Message----- From: Simon Cozens To: [EMAIL PROTECTED] Sent: 10/6/2001 7:50 AM Subject: vtable.h I've just committed some files which generate vtable.h; these were actually left over from my experiments of a *long* time ago. [1] It might need quite a few changes, but it's a good start, and I think it's general enough to survive. The next thing I want to do with it is have something akin to process_op_func.pl which takes a macro-ized description of the vtable functions and turns them into real C code. Volunteers welcome, or I'll write it myself. :) This could be a good place, however, for newcomers to Parrot to get involved with something relatively straightforward but pretty crucial. Hint, hint... Simon [1] In short, back in the beginning, Dan and I independently started implementing Parrot; Dan's version was more complete and sensible by the time we got together to discuss it, so his became the codebase that was checked into CVS. Dan had started with the interpreter main loop and ops, and I had started with PMCs. -- Actually Perl *can* be a Bondage & Discipline language but it's unique among such languages in that it lets you use safe words. -- Piers Cawley
