Idiom for a class and an object in Ada

[Marin David Condic <nobody@noplace.com>]

Suppose I have a class with one or a limited set of objects. The objects 
are "global" in the sense that they hang around from program startup 
thru the entire life of execution. An example would be an A/D Converter 
class - My little control box might have 3 or 4 A/Ds in it - they're 
always there and I want the data associated with them to be static (not 
declared on the stack.)

Question: What is the preferred Ada idiom for defining such a creature?

I have a package that defines the class - that contains the tagged type 
and any methods. I might:

a) Declare the objects within that "class" package

b) Declare the objects within some child package of the class package

c) Declare the objects in some global "Here's all my static data" 
package (not very tidy)

d) Declare the objects in the main program (not good if they are 
accessed by more than one task and also a kind of dumping ground)

Does anybody have an opinion or experience with doing this? I know what 
I've done in the past, but I'm curious if there is any preferred method 
or idiom for this in the OO paradigm as applied to Ada?

MDC
-- 
======================================================================
Marin David Condic
I work for: http://www.belcan.com/
My project is: http://www.jsf.mil/NSFrames.htm

Send Replies To: m   o   d   c @ a   m   o   g
                    c   n   i       c   .   r

     "Power corrupts.  Absolute power is kind of neat"
         -- John Lehman, Secretary of the Navy 1981-1987
======================================================================