Re: Idiom for a class and an object in Ada

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

I chose the A/D converter example because I needed to think of something 
that exists statically in some fixed number within a system and is 
highly unlikely to change over time. I might have gone political and 
used "Senate Seats" since there are only 50 of them and (depending on 
the application in mind) will likely be some kind of fixed objects from 
start to finish.

I'm really sorry people got wrapped around the axle of the A/D stuff 
because I was looking for a more general answer to a more general 
question about OO Programming in Ada.

That said, I thought your remarks were well thought out anyway. ;-)

MDC

Michael Paus wrote:

> You have chosen to use a tagged type to represent your A/D converters
> which I think is a wise decision but neither you nor anybody else
> seems to be able to give a good reason for that (if I have not missed it 
> :-)
> and also in the way you have started you are missing an opportunity
> for flexibility in your design and for really exploiting your OO approach.

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