From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=3.0 tests=BAYES_20 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 10 Sep 93 14:00:06 GMT
From: haven.umd.edu!news.umbc.edu!nobody@uunet.uu.net  (Mike Berman)
Subject: Re: Don't we already have a 'Valid? (was Re: Unchecked_Conversion...)
Message-ID: <26q196INNl1t@umbc4.umbc.edu>
List-Id: <comp.lang.ada>

Apologies for following up my own posting, but I've already received
some e-mail on the topic and thought I'd clear up some ambiguities.

The prior discussion on unchecked_conversion has quite adequately
explained why the code I excerpted operates the way it does. The result
of the unchecked_conversion makes the program erroneous if it is not a
valid member of the target type.

The real question is why does the "type_mark" form of the "in" operator
exist? Most people use "in" solely for checking ranges within a scalar
type, but it is defined to operate on _any_ type. Since it can't be used
to check the results of unchecked_conversions, then why is it defined
for nonscalar types?

And, as the subject line suggests, why not use the already-defined
syntax for the "in" operator _instead_ of adding the 'Valid attribute?

-- 
Mike Berman
University of Maryland, Baltimore County     Fastrak Training, Inc.
berman@umbc.edu                              (301)924-0050
       The views represented in the above post are my own.