Hi Samuele,
with your help, I can now handle my extra fields in arbitrary
instances very well. One problem remains:
(see test_wrapping)
The support function is no longer a simple thing, but it
contains a decision, so I need two blocks.
In test_wrapper, I solved this by making wrap_obj a high
Hi Samuele,
with your help, I can now handle my extra fields in arbitrary
instances very well. One problem remains:
(see test_wrapping)
The support function is no longer a simple thing, but it
contains a decision, so I need two blocks.
In test_wrapper, I solved this by making wrap_obj a high
Hi Christian,
There is something wrong whenever anyone is getting close to hlinvoke()
:-)
I don't understand your problem well enough (and will let Samuele answer
if my answer is not sufficient), but:
On Wed, Mar 29, 2006 at 12:11:48AM -0800, Christian Tismer wrote:
In the real implementation,
what: weekly pypy-sync meeting
where: #pypy-sync on freenode
when: 2006-03-30, 5pm Central European Time for 30 minutes
who: all active PyPy developers
topics:
- activity reports
- the status of uthreads. It is needed by the logic implementation.
- is it premature to think about setting up a
On onsdag 29 mars 2006 16:39, Anders Lehmann wrote:
what: weekly pypy-sync meeting
where: #pypy-sync on freenode
when: 2006-03-30, 5pm Central European Time for 30 minutes
who: all active PyPy developers
topics:
- activity reports
- the status of uthreads. It is needed by the logic
Hi,
I have some doubts about the semantic of some low level operations I
have found during my development of the CLI backend.
The first doubt is about overflow-checked operations: I've noticed there
are a number of checked operations that can never fail due to their
semantic, such as
Antonio Cuni wrote:
Finally, the last question is ootypesystem-specific: I've noticed that
the rtyper sets the 'meta' field of every instance just after it has
been created: what does it contain? It seems to me that it contains the
class the object belongs to: am I correct? If so I could
Hi Samuele,
On 3/29/06, Samuele Pedroni [EMAIL PROTECTED] wrote:
this meta field can contain instances that have further fields beyond
class_. class_ contains something of type ootype.Class, what is expected
to be the runtime representation of a class in the backend type system,
The extra
