Re: [PATCH] Use the "O!" format more in the Python code

[Tom Tromey <tom@tromey.com>]

>>>>> "Paul" == Paul Koning <paulkoning@comcast.net> writes:

Paul> Also, any type can be subclassed.  That
Paul> last point is not true for types defined in C code, unless the code
Paul> allows it to happen.  In general it should do so; it's very rare
Paul> indeed for it to be "the right thing" for a type not to allow
Paul> subclasses.

In gdb we've been fairly selective with this.

I looked it up and you have to set Py_TPFLAGS_BASETYPE, which we do in
13 of the classes that gdb implements.

Maybe we should do this everywhere?  But if we did that then wouldn't we
also want to implement the 'dict' feature everywhere as well?

I'm not sure there's a big advantage to it or need for it though.
So maybe it's just busy-work.


I've been hoping to transition the internal types to be real C++ types,
like give them constructors and destructors, initializers, etc.  But
maybe it's not really possible with the Python lifetime model, at least
when subclassing is available.

Tom