1.1 --- a/docs/concepts.txt Fri Jun 12 22:03:56 2009 +0200
1.2 +++ b/docs/concepts.txt Sun Jun 14 01:18:05 2009 +0200
1.3 @@ -26,6 +26,13 @@
1.4 permitting the use of tables (described below). Module and class attributes
1.5 can also be finalised in this way in order to permit certain optimisations.
1.6
1.7 +An additional restriction required for the current implementation of tables
1.8 +(as described below) applies to class definitions: each class must be defined
1.9 +using a unique name; repeated definition of classes having the same name is
1.10 +thus not permitted. This restriction arises from the use of the "full name" of
1.11 +a class as a key to the object table, where the full name is a qualified path
1.12 +via the module hierarchy ending with the name of the class.
1.13 +
1.14 See rejected.txt for complicating mechanisms which could be applied to
1.15 mitigate the effects of these restrictions on optimisations.
1.16