Fwd: PBC, Const Tables, and STRINGs
kjstol
parrotcode at gmail.com
Tue Apr 27 11:22:56 UTC 2010
chromatic,
just for my understanding (and other lurkers perhaps), you mean that a
Sub is now stored in the constant table as a Sub PMC, and each of its
attributes is stored as other constants (mostly STRINGs), and you
would prefer to make that one blob? Basically, rather than a "graph"
of constants (root is the Sub PMC and it has indexes to other entries
in the constant table), it becomes one PMC that represents everything
the sub needs/has (such as the various names for the sub :flags). Is
this correct?
kjs
On Mon, Apr 26, 2010 at 6:21 AM, chromatic <chromatic at wgz.org> wrote:
> On Sunday 25 April 2010 at 18:49, Vasily Chekalkin wrote:
>
>> Simple transition of PMCs across wire. E.g. "Erlang-on-parrot" or
>> "Pass-by-value" in CORBA world.
>>
>> (I'm not talking about keeping such feature.)
>
> In the specific case of Sub PMCs, we'd have to transfer bytecode anyway, but I
> take the point for simpler PMCs... but transferring an Object or a PMC written
> in PIR gets complex too.
>
> -- c
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
More information about the parrot-dev
mailing list