On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > On Tue, 22 Jun 2004, Leopold Toetsch wrote:
> >> I think both should use just interpreter->class_hash. OTOH putting PMC
> >> names into this one hash makes it more likely that we get name
> >> collisions for user class names.
>
> > Yeah. We probably ought to go rename the PMC classes to have Parrot
> > prefixes.
>
> Ack. But ParrotResizableIntegerArray :(
Yeah, I know. It's nasty. :(
I suppose for internal things we could use a "non-legal" prefix character
in the name instead. Something like |Integer or :Integer. That's nasty
too, though, in its own way.
> > We don't need a __repr__ method. That's just an alternate freeze format.
> > (Arguably we need a parameter to freeze to note which format to use)
>
> I beg to differ. __repr__ is too universally used in Python. It's a
> distinct method. A different freeze format is of course doable, but
> overriding the C<repr> vtable method make this implementation a PITA.
I just went digging through the docs to make sure I knew what was going
on. __repr__ is the python-visible name for our get_string vtable method.
We don't need any support beyond tying names together in the namespaces,
so far as I can see.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
