[Python-Dev] A little GC confusion
David Abrahams
David Abrahams" <david.abrahams@rcn.com
Thu, 21 Feb 2002 10:16:24 -0500
Thu, 21 Feb 2002 10:16:24 -0500
- Previous message: [Python-Dev] A little GC confusion
- Next message: [Python-Dev] A little GC confusion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
----- Original Message ----- From: "Thomas Heller" <thomas.heller@ion-tof.com> To: "David Abrahams" <david.abrahams@rcn.com>; <python-dev@python.org> Sent: Thursday, February 21, 2002 10:01 AM Subject: Re: [Python-Dev] A little GC confusion > > > I'm not really sure, but it seems your code does not crash any longer > > > if you remove the Py_TPFLAGS_HAVE_GC from your definition of > > class_metatype_object. > > > > Yes, I'm aware of that. What I don't understand is how the builtin metatype > > gets away with Py_TPFLAGS_HAVE_GC when some of its instance types are not > > even heap-allocated. > > > Hm, I don't understand you, Are you talking about Py_TPFLAGS_HEAPTYPE? No, please re-read my initial posting. Py_TPFLAGS_HAVE_GC places requirements on the allocation method of instances, at least according to the docs.
- Previous message: [Python-Dev] A little GC confusion
- Next message: [Python-Dev] A little GC confusion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]