#1020: subclassing pmc from pir + lot more
-----------------------------+----------------------------------------------
Reporter: jessevdam | Type: RFC
Status: new | Priority: normal
Milestone: | Component: core
Version: 1.6.0 | Severity: medium
Keywords: subclass typeof | Lang:
Patch: | Platform: all
-----------------------------+----------------------------------------------
Changes (by whiteknight):
* type: bug => RFC
Comment:
It's a very interesting plan, very ambitious though. While the details are
certainly going to need careful review, I think the gist of this plan is
something that we really should consider in the long run.
We don't want to recurse runloops for every single VTABLE call on every
single PMC like we have to do now with Object.pmc. The only way to get
this working is to implemented Lorito and use Lorito to implement large
amounts of Parrot (ops, several support routines, etc). Once we have that,
we would need to declare that VTABLEs can only be called through Lorito,
never from C. This is going to require a major refactor of our current API
across the board.
This is also not to mention that there is currently going to be a speed
penalty when things are implemented in PIR/Lorito instead of in pure C. I
have high hopes that converting everything to Lorito (to avoid messy
context switches) and optimizing heavily will actually make a Lorito-based
solution faster in the long run. But until we reach that "long run" point,
things would slow down significantly.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1020#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
