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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,56760b0ebeac6ba1
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Need of help Leonid(dulman@ibm.net)
Date: 1997/02/12
Message-ID: <dewar.855750810@merv>#1/1
X-Deja-AN: 218250115
References: <5dhbjt$hbe@news.ibm.net.il> <dewar.855436299@merv>
 <u8n2tdm68y.fsf@ehmgs2.et.tu-dresden.de> <dewar.855571664@merv>
 <5dpftl$qi@fozzie.sun3.iaf.nl>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-02-12T00:00:00+00:00
List-Id: <comp.lang.ada>


Geert said

<<Of course when this package is instantiated with a 32-bit integer type
it doesn't make sense to use the full set on many machines, but IMHO it
is fine to instantiate the package. Only when a program uses operations
on Set from the instantiated generic a warning should be given.
>>

Well a general point on warnings is that they are warnings and not errors
precisely because you can't be sure they are errors. I disagree that the
warning in the generic case is inappropriate. If you create this
instantiation, it is useful to know that it may have limited use AT THE
TIME YOU CREATE IT, not later when you instantiate it.

You can always use pragma Warnings (Off) before the particular declaration
and pragma Warnings (On) after it to kill a specific warning.

You can never satisfy everyone with warnings, since some people want to be
warned more than others :-)