[pypy-dev] Build and test failures

Ben.Young at risk.sungard.com Ben.Young at risk.sungard.com
Fri Jul 22 10:18:56 CEST 2005

Armin Rigo <arigo at tunes.org> wrote on 21/07/2005 18:51:28:

> Hi Ben,

Snip ...

> The flow graph viewer doesn't show all this, because it doesn't really
> display complex low-level types and constants nicely.  Not sure if and
> how to improve that...
> > I don't really understand the PBC side of things. Is there a reason 
> > the object hierarchy can't just mirror the way CPython does it? Or 
> > that be too slow?
> Yes, we are indeed trying for each kind of PBC family to figure out the
> best C-ish equivalent.  A family of functions should become just a C
> function pointer; a family of classes should become a vtable pointer;
> etc.  We always planned to do that, and our RPython code is written
> accordingly, but the devil's in the details...

So is a family of classes the set of any classes that can be assigned to a 
particular instance variable, even if they dont share a common base?


class A:

class B:

foo = somebool ? A() : B()

Would it be simpler to require that all instances must at least be 
annotated to a common base, and fail to annotate if a not-base-defined 
method is called on the instance. Or is that really what you are already 

Do function PBCs all have to have the same signature, or can it vary?

Anyway, thanks for the reply! As illuminating as ever. I guess with the 
rtyping, the first flush of exciting coding has gone and you are down to 
the grinding out bugs stage. Are you pleased with the way things have gone 
or are there any chages you would make to the architecture now?


P.S os.ftruncate doesn't exist on windows I'm afraid, so most of the tests 
fail at the moment

> A bientot,
> Armin

More information about the Pypy-dev mailing list