Re: Anachronistic Acronyms in Parrot?

[Dan Sugalski]

At 06:35 PM 9/25/2001 -0700, Paul Prescod wrote:
>Dan Sugalski wrote:
> >
> > At 12:01 AM 9/25/2001 +0200, Samuele Pedroni wrote:
> >
> > > > The other subtle difference, now that I think about it, is a bug in
> > > Parrot; I
> > > > wasn't planning to garbage collect vtables the same way that we GC 
> PMCs.
> > >The python way is more so, vtables (PyTypeObjects) are PMC (PyObjects).
> > >
> > >So types are first-class objects.
> >
> > Not at the Parrot level they aren't. They might be faked out to be so at
> > the Perl/Python/Ruby level, though.
>
>What is the downside of having types be first-class objects at the
>Parrot level?

Seems like a lot of overhead for a table of function pointers. If nothing 
else there's another level of indirection there, since the 
variable/object/whatever header and body are separate.

                                        Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk