RE: [pythonesque] vtable ideas

2002-02-03 Thread Angel Faus
Simon said: > > I see. ?But what's the rational to have Bigints / Bigfloat be native types > > instead of PMCs? > > They're useful and predictable. And also, you may want to automatically > promote integers to bigints; you probably don't want to automatically > promote integers to complex types.

Re: [pythonesque] vtable ideas

2002-02-03 Thread Simon Cozens
begin quote from Angel Faus: > I see. ?But what's the rational to have Bigints / Bigfloat be native types > instead of PMCs? They're useful and predictable. And also, you may want to automatically promote integers to bigints; you probably don't want to automatically promote integers to complex ty

RE: [pythonesque] vtable ideas

2002-02-03 Thread Angel Faus
> > These methods are provided so that we can play with "native" types in our > bytecode then send them to our pmc, as otherwise every constant in our > code would have to be a PMC, which is a little excessive. > > Things like a complex number will be represented by either a PMC class > (very lik

Re: [pythonesque] vtable ideas

2002-02-02 Thread Alex Gough
On Sun, 3 Feb 2002, Angel Faus wrote: > I. Missing methods in parrot: > > The are many vtable methods in python not present in parrot. Some of the > ones I would expect to really be needed are: > >* divmod# integer division >* power >* absolute >* invert >* compare Yes, w

[pythonesque] vtable ideas

2002-02-02 Thread Angel Faus
Hi all- I have been checking the Python source code (something I am sure all of you already have done :-) and some differences on the design surprised me so much that I decided to come and make some questions. I guess that most of you know well the python source code, so please apologize the len