On Fri, Mar 25, 2005 at 11:31:58AM +0100, Leopold Toetsch wrote:
> Matt Diephouse <[EMAIL PROTECTED]> wrote:
> > Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> >> Seems to be another ordering problem, where a hash is used instead of an
> >> array with inherited vtable methods. pylong.dump has already the wrong
> >> entry:
> >>
> >> 'destroy' => 'default',
> >>
> >> in the suoer hash.
>
> > I don't think it's an ordering problem (and I can say that now that
> > I've read all the code closely). 'default' isn't used when pmc2c2.pl
> > is searching for inherited vtable methods: it's only used when none of
> > the super classes contains a method by that name.
>
> pmclass PyLong extends BigInt dynpmc group python_group {
> ^^^^^^
> void
> Parrot_BigInt_destroy(Interp* interpreter, PMC* pmc)
> {
> ...
> Parrot_BigInt_destroy,
>
> As the behavior is different on two of my machines, it still smells like
> an hash-related ordering issue.
I had a quick look and things looked ok. The parents are stored in a
hash but they are retrieved sorted by their value which increments as
parents are added.
What was different between the 2 machines ( perl versions/os/whatever )?
Peter
--
Our mission is to continually administrate performance based resources
in order that we may authoritatively initiate value-added information for
100% customer satisfaction
