Klaas-Jan Stol wrote:
1a: when are set_pointer and get_pointer actually called?
From pmc.c:pmc_new
1b: in set_pointer (I copied it from None.pmc) an assertion is done. Why
is this? (this is also part of question 1a: set_pointer is called once,
apparently?)
Well, it asserts that you really
Leopold Toetsch wrote:
Klaas-Jan Stol wrote:
mmm, I looked at classes/none.pmc, this is a copy/paste:
===
#include
static PMC * Py_None;
pmclass None singleton {
Ah, yep - None is a singleton too - sorry for my confusion.
So it should be rather easy to subclass None, impleme
Klaas-Jan Stol wrote:
mmm, I looked at classes/none.pmc, this is a copy/paste:
===
#include
static PMC * Py_None;
pmclass None singleton {
Ah, yep - None is a singleton too - sorry for my confusion.
So it should be rather easy to subclass None, implement get/set_pointer
and us
Leopold Toetsch wrote:
Klaas-Jan Stol wrote:
Suppose I would want to have my own custom representation of "None".
What should I do to have my child class be a singleton too? (just
extending singleton as well?)
None isn't a singleton. But have a look at the Null PMC or better
env.pmc.
Klaas-Jan Stol wrote:
Suppose I would want to have my own custom representation of "None".
What should I do to have my child class be a singleton too? (just
extending singleton as well?)
None isn't a singleton. But have a look at the Null PMC or better env.pmc.
$ grep singletion classes/*.
hi,
Will Coleda wrote:
On Jul 27, 2005, at 4:00 PM, Klaas-Jan Stol wrote:
hi,
Is there any documentation about the complete syntax for pmc files
when writing PMCs (this time in C)?
I think that's technically the only way to write PMCs. (things
written in PIR are Objects). And, as you
On Jul 27, 2005, at 4:00 PM, Klaas-Jan Stol wrote:
hi,
Is there any documentation about the complete syntax for pmc files
when writing PMCs (this time in C)?
I think that's technically the only way to write PMCs. (things
written in PIR are Objects). And, as you've seen, pmc2c.pl is
cu
