Dan Sugalski wrote:
> Okay, here's the VTABLE PDD. Comments, please. (As if there's any worry
> about not having any.... :)
Hi, Dan.
I have a _very_ different view of yours on the vtable area. I read your PDD,
but I really couldn't figure out how the operations would be carried. For
instance, on the add function, I have to sum PMC2 and PMC3 and store it in
PMC1. I should use the vtable of PMC1, PMC2 or PMC3? If I use the one of
PMC1, it wouldn't (shouldn't) know about the internal structure of PMC2 and
PMC3, and if I use the vtable of PMC2 or PMC3, it wouldn't know what how to
store the value on PMC1 (say if PMC1 is tied and the value should actually
be written to a database?).
I have a thought of making vtables very near to the current (Perl 5.6)
interface for ties and overload. Of course that interface could be designed
a little better if we dive into it, but I think it's ok to start with...
Anyway, I see if I'll write something about my ideas, and I send it to the
list later.
Thanks,
- Branden
