On Mon, Feb 22, 2010 at 5:38 PM, Peter Lobsinger <[email protected]> wrote: >> Seems you're right. pmc2c generates the pcc boilerplate and doesn't >> delegate to nci. I was confused by references to pmc methods in >> config/gen/call_list/* and the fact that pmc2c calls these functions >> "Parrot_${pmc_name}_nci_${method_name}". > > Turns out even this isn't strictly true. pmc2c generates pcc > boilerplate for regular methods, but delegates to NCI for multis. I > don't know why. This should probably be changed at some point to be > consistent one way or the other (I'm biased towards delegating to NCI > for obvious reasons).
Well, that's interesting. Personally I think we should try to standardize on the PCC method for a variety of reasons. Standardizing on a single code path lets us get rid of a lot of mode-switching cod, let's us focus optimization efforts on a single hotpath, and takes some stress off the NCI system that will give us more freedom to refactor and improve that system. What might make for a good interim measure would be to examine the system and see what would be needed to standardize one way or another. We can make a better decision once we know more. --Andrew Whitworth _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
