|
| virtual bool | accepts (PyObject *pyob) const |
| | Accept any reference the mapping protocol supports.
|
| virtual void | setItem (const HxStr &key, const Object &value) |
| | Store a value under a name.
|
| virtual void | setItem (const Object &key, const Object &value) |
| | Store a value under a key object.
|
| | Object (PyObject *pyob=Py_None) |
| | Take a borrowed reference and add a count of its own.
|
| | Object (const Object &other) |
| | Copy another handle and add a count of its own.
|
| virtual | ~Object () |
| | Release the reference.
|
| Object & | operator= (const Object &other) |
| | Replace the reference with another handle's.
|
| Object | getAttr (const HxStr &name) const |
| | Read one attribute.
|
| String | str () const |
| | Produce the text of str() applied to the object.
|
| HxStr | as_string () const |
| | Produce the text of str() applied to the object, as a game string.
|
| Type | type () const |
| | Produce the object's type.
|
| bool | isType (const Type &type) const |
| | Report whether the object's type is a given type.
|
| bool | isTuple () const |
| | Report whether the object is a tuple.
|
| bool | isList () const |
| | Report whether the object is a list.
|
template<typename T>
class Py::MapBase< T >
Handle on any Python mapping, and the base of Py::Dict.
One instantiation exists in the image, Py::MapBase<Py::Object>, with its descriptor at 0x009029a0, deriving from Py::Object at offset 0.
The vtable at 0x00825848, copied at 0x00833278, has five entries, the three Py::Object slots plus two of its own.
| Slot | Member | Address |
| 0 | compiler-generated type function | 0x0050d0b0 |
| 1 | inherited destructor | 0x0050d038 |
| 2 | accepts | 0x0050d7f8 |
| 3 | setItem taking a name | 0x0050d6f8 |
| 4 | setItem taking a key object | 0x0050d780 |
Both setItem() bodies are shared with Py::Dict rather than overridden, so the derived table repeats the same two addresses.
Released PyCXX declares a reading half as well, with size(), getItem(), and a mapping reference proxy. None of it is in the table, so none is reconstructed. The image therefore establishes that this instantiation is write-only.