On Fri, Feb 26, 2010 at 2:22 PM, Peter Lobsinger <[email protected]> wrote: > What I'm getting at is that pmc2c hides information from the rest of > the system. AFAICT, you cannot obtain the PCC signature of raw/managed > methods, because the wrapping NCI pmc has no information about them. > When the wrapping NCI pmc knows the NCI signature, it can generate the > PCC signature for the function from the given NCI signature. In fact, > it must generate a pcc signature for a runtime frame builder to work > correctly. > > Here's an example using arity: > > ...
So that's definitely a bug, from where I am standing. The NCI PMC should contain information about the PCC signature of the method. > I like the 2 pmc solution solution. I'm liking it much better too. Combine that with some much-needed improvements to Pmc2c, and we should be in a much better place. --Andrew Whitworth _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
