Show
Ignore:
Timestamp:
04/25/08 16:13:48 (5 months ago)
Author:
pmoura
Message:

Minor documentation updates.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • trunk/examples/proxies/NOTES.txt

    r4102 r4225  
    2727object parameters. They may be stored on the database as Prolog facts. This  
    2828results in a very compact representation, which can be an advantage when  
    29 dealing with a large number of objects with immutable state. However, this is  
    30 also a fragile solution as changes on the parametric object ancestors may  
    31 imply changes to the number and meaning of the parametric object parameters  
    32 which, in turn, may imply changes to all the Prolog facts used to represent  
    33 the individual objects. 
     29dealing with a large number of objects with immutable state. In addition, all  
     30the predicates dealing managing these compact representation are encapsulated  
     31in a parametric object. This can be, however, a fragile solution as changes on 
     32the parametric object ancestors may imply changes to the number and meaning of 
     33the parametric object parameters which, in turn, may imply changes to all the  
     34Prolog facts used to represent the individual objects. 
     35 
     36Note that parametric objects can co-exist with "normal" objects. For example,  
     37when using a class-based design, we may use "normal" instances together with 
     38a parametric instance of the same class.