#905: [RFC] Deprecate Eval PMC
---------------------+------------------------------------------------------
Reporter: allison | Owner:
Type: RFC | Status: new
Priority: normal | Milestone:
Component: none | Version: 1.4.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by pmichaud):
Just to present a possible counter-argument; one of the possible
advantages of the current "return an Eval PMC" approach is that it's
possible for a HLL to introspect the returned Eval PMC and do any
additional linking or setup that may be needed on the newly-compiled subs.
If compiling source code instead chooses to return only a single Sub PMC,
we lose that capability.
In particular, in Rakudo the eval() function has to compile a string which
may create one or more subs, and then set the :outer context on the things
that come back.... and it's definitely *not* the Sub marked :main that
gets its outer context set (nor should it be, as that sub is not the HLL
mainline code).
Pm
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/905#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets