1.1 --- a/docs/structures.txt Sun Jan 25 02:56:16 2009 +0100
1.2 +++ b/docs/structures.txt Mon Jan 26 01:25:30 2009 +0100
1.3 @@ -273,6 +273,8 @@
1.4 effectively be a matrix with each dimension indexed using the same sequence of
1.5 codes for each of the classes in a program.
1.6
1.7 -An alternative might be to insert descendants as special attributes into the
1.8 -object/attribute lookup table. This would also require an extra key to be
1.9 -retained, since each class would have its own attribute code.
1.10 +The current solution is to insert descendants as special attributes into the
1.11 +object/attribute lookup table. This requires an extra key to be retained,
1.12 +since each class must provide its own attribute code such that upon an
1.13 +instance/class compatibility test, the code may be obtained and used in the
1.14 +object table.