#1475: [Pmc2c] make METHOD and MULTI consistent in terms of how PCC is done
----------------------+-----------------------------------------------------
Reporter: plobsing | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: pmc2c | Version: 2.1.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Comment(by plobsing):
Replying to [ticket:1475 plobsing]:
> Currently, pmc2c generates the boilerplate to do PCC stuff in methods.
However, if the method is multi, pmc2c uses NCI to do PCC.
>
> There are likely advantages and disadvantages to both approaches
(duplicate code vs potential object system bootstrapping issues). One
thing is clear to me: whichever mechanism is used, these should be doing
things the same way.
This was discussed in a thread that went somewhat off-topic on the parrot-
dev mailing list, [http://groups.google.com/group/parrot-
dev/browse_thread/thread/65f717293fcec6db# '[RFC] removing library NCI
signatures from core']. Some points that came out of the discussion were:
* NCI thunks don't (and shouldn't) cover all of the PCC functionality
required by methods, so methods shouldn't use NCI thunks.
* Thunked and raw NCI are fundamentally different and should have
different supporting PMCs to make this distinction, to simplify
implementation, and to allow raw NCI to provide signature introspection.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1475#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
