# HG changeset patch # User Paul Boddie # Date 1366402502 -7200 # Node ID 32134fe3d5b6de0941a7bb6695836330629845f2 # Parent a0188e11e3d8e7ac19670761a3729a751bd044a2 Removed the note about restrictions on class naming since the object table can now accommodate multiple forms of the same name. diff -r a0188e11e3d8 -r 32134fe3d5b6 docs/concepts.txt --- a/docs/concepts.txt Fri Apr 19 22:07:36 2013 +0200 +++ b/docs/concepts.txt Fri Apr 19 22:15:02 2013 +0200 @@ -29,13 +29,6 @@ permitting the use of tables (described below). Module and class attributes can also be finalised in this way in order to permit certain optimisations. -An additional restriction required for the current implementation of tables -(as described below) applies to class definitions: each class must be defined -using a unique name; repeated definition of classes having the same name is -thus not permitted. This restriction arises from the use of the "full name" of -a class as a key to the object table, where the full name is a qualified path -via the module hierarchy ending with the name of the class. - Rebinding of attributes outside classes and modules can be allowed if attribute usage observations are being used to detect such external modifications to such objects. Without such observations, such rebinding