1.1 --- a/docs/concepts.txt Mon Jun 08 00:49:37 2009 +0200
1.2 +++ b/docs/concepts.txt Fri Jun 12 22:03:56 2009 +0200
1.3 @@ -212,7 +212,10 @@
1.4 The locations stored in table/list elements are for instance attributes
1.5 relative to the location of the instance, whereas those for class attributes
1.6 and modules are absolute addresses (although these could also be changed to
1.7 -object-relative locations).
1.8 +object-relative locations). Thus, each occupied table cell has the following
1.9 +structure:
1.10 +
1.11 + attrcode, uses-absolute-address, address (or location)
1.12
1.13 Objects and Structures
1.14 ======================
1.15 @@ -247,10 +250,12 @@
1.16
1.17 Used to test instances for membership of classes (or descendants of classes).
1.18
1.19 -Since, in traditional Python, classes are only ever instances of the "type"
1.20 -built-in class, support for testing such a relationship directly has been
1.21 +Since, in traditional Python, classes are only ever instances of some generic
1.22 +built-in type, support for testing such a relationship directly has been
1.23 removed and the attrcode is not specified for classes: the presence of an
1.24 -attrcode indicates that a given object is an instance.
1.25 +attrcode indicates that a given object is an instance. In addition, support
1.26 +has also been removed for testing modules in the same way, meaning that the
1.27 +attrcode is also not specified for modules.
1.28
1.29 See the "Testing Instance Compatibility with Classes (Attrcode)" section below
1.30 for details of attrcodes.