From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,901038687c38f61c
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!peer01.cox.net!cox.net!newsfeeds.sol.net!posts.news.twtelecom.net!nnrp2.twtelecom.net!not-for-mail
From: "Matthew Heaney" <mheaney@on2.com>
Newsgroups: comp.lang.ada
References: <M3Ocd.237$5i5.72@newsread2.news.atl.earthlink.net>
 <cl6395$g1l$1@online.de>
Subject: Re: Idiom for a class and an object in Ada
Date: Wed, 20 Oct 2004 13:15:18 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <41769d26$0$91009$39cecf19@news.twtelecom.net>
Organization: Time-Warner Telecom
NNTP-Posting-Date: 20 Oct 2004 17:15:19 GMT
NNTP-Posting-Host: 357b086d.news.twtelecom.net
X-Trace: 
 DXC=0XJe^l_m;>jE0G1fKX\WG`C_A=>8kQj6mhHXa^^g6TZddH4leX5AV6ddYZAA8S:<l`Ne2kQL2i2Ob
X-Complaints-To: abuse@twtelecom.net
Xref: g2news1.google.com comp.lang.ada:5535
Date: 2004-10-20T17:15:19+00:00
List-Id: <comp.lang.ada>


"Michael Paus" <pausnospam@nospamib-paus.com> wrote in message 
news:cl6395$g1l$1@online.de...
>
> 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.

How are you able to evaluate whether the use of a tagged type is a "wise 
decision" unless you have been given reasons why the type is tagged?

My judgement about the fact that the type is tagged and nonlimited is that 
this is a very *unwise* decision.

There is no reason for the type to be tagged unless you need type extension 
or dynamic binding.

There is no reason why the global objects' type should have assignment.

There is no reason why the global objects' type should allow anyone to 
create instances anywhere.