Re: Private Child Unit

[gauthier@unilim.fr (Michel Gauthier)]

In article <329DB71E.59E2B600@avions.aerospatiale.fr>, Paul Chardon
<paul.chardon@avions.aerospatiale.fr> wrote:

>>          Just to understand correctly the need of that concept, can
anyone give
>>  me a significant example of use of a private child unit.

1= Assume a component P, or a hierarchy rooted thereof.
 Assume the body (or bodies) contains messages intended to
be displayed to some user.
 A private child P.Messages can be sensible to group these
messages in a way such that :
 - the messages are outside genericity (and possible constant duplication),
 - translated versions can be easily written.

2= Assume an abstract class with polymorphic implementations
declared in childs.
 Assume a collection of class-wide non-exported subprograms that are
called in some, but not all child bodies.
 A private child can be a choice better than declaring this collection
in the private part of the root.

However, I found many cases of generic units that are conceptually 
private, but cannot be private childs because they have to be 
instantiated in private parts (in order to re-export the type).

----------          ----------          ----------          ---------- 
Michel Gauthier / Laboratoire d'informatique
123 avenue Albert Thomas / F-87060 Limoges
telephone + 33 () 05 55 45 73 35  [or ~ 72 32]
fax +33 () 05 55 45 73 15  [or ~72 01]  
    no initial zero from abroad ! ! !
----------          ----------          ----------          ----------
Si l'an 2000 est pour vous un mysticisme stupide, utilisez la base 9
If you feel year 2000 a stupid mystic craze, use numeration base 9
----------          ----------          ----------          ----------