Re: Idiom for a class and an object in Ada

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

Well, that's one approach. I'd prefer to avoid the code bloat of a 
generic when all I really need to duplicate is the data. Also, its 
tougher to do any sort of inheritance going the generic route. I'm 
wondering specifically about the usual OOD idiom of making a class out 
of a package with a tagged record - such that it can be extended with 
another child class - and where is the "best" place to declare objects 
of that class?

MDC

Marius Amado Alves wrote:
>> 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?
> 
> 
> generic
>    Line : Number;
> package AD_Converter is
>    function OK return Boolean;
>    function Get return Value;
> end;
> 
> package Heat is new AD_Converter (123);
> package Noise is new AD_Converter (456);
> package Wind is new AD_Converter (789);
> 
> -- You can't get more "static" than that!
> 

-- 
======================================================================
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
======================================================================