Sam Ruby wrote:
I've made a clone of these functions, and made the relevant fixes to my copy.
As you said, that's your time. You can clone half of Parrot core for experiments.
Hopefully someday this will get refactored back into Parrot.
The code for running PASM/PIR code is fine.
The second time I called Parrot_run_meth_fromc_args, it was with an NCI method. The only problem is ...
... that you are calling the wrong function during your handrolled and unneeded redispatch. Why are you are creating a return continuation for calling a C function? Why do you pass registers according to pdd03 to a C function? Why do you execute a C function with a new context structure?
*runops_args* is running *opcodes*. A NCI fuction is a thin wrapper around a piece of C code.
I am not interested in discussing this any more.
Sam, it's a big difficult to tell you that the current approach of implementing Python will not work, because as soon as I say so, you gonna stop discussing necessary issues.
The current Parrot has bugs. I've notified you of a number of them.
Sure - And, yes, thanks your notice I've fixed one today.
... You are apparently not interested as you would prefer to rewrite Parrot instead.
Make it workable. Complete. Which admittedly needs some rewrite, yes. Such is life.
Undoubtably, at that time it will have a different set of bugs. At which point, undoubtably, the process will repeat.
No, there are of course no bugs in Parrot final, never ;)
Onward.
- Sam Ruby
leo
