Stefan Behnel wrote:
We create a new struct for the type that contains the parent-struct as first field, and then we add the new attributes of the new type behind that.
I seem to remember there's a field in the type called tp_basicsize that's meant to indicate how big the base part of the struct is, with any variable-size part placed after it. If a variable-size type always uses this field to find the variable data, it seems to me that the usual scheme for subclassing should still work, with the extra fields existing in between those of the base class and the new position of the variable data. Does Py_Unicode not take notice of this field? If not, maybe that's something that should be fixed. -- Greg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
