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,45a9122ddf5fcf5 X-Google-Attributes: gid103376,public From: mheaney@ni.net (Matthew Heaney) Subject: Re: Rules for Representation of Subtypes Date: 1996/09/29 Message-ID: #1/1 X-Deja-AN: 186070407 references: <1996Sep26.191257.1@eisner> <1996Sep28.155354.1@eisner> content-type: text/plain; charset=ISO-8859-1 organization: Estormza Software mime-version: 1.0 newsgroups: comp.lang.ada Date: 1996-09-29T00:00:00+00:00 List-Id: In article , bobduff@world.std.com (Robert A Duff) wrote: >In article <1996Sep28.155354.1@eisner>, >Larry Kilgallen wrote: >>If the assignment of the output causes erroneousness, >>then why isn't the name of the operation Checked Conversion ? > >Heh? If it were checked, it would do something sensible, like raise an >exception, or return a well-defined result, or give a compile-time >error. The UNchecked means, it's *not* checked -- if you do something >wrong, you get unpredictable behavior, i.e. erroneous execution. I think his comment was in reaction a previous post, which stated that the compiler would make all kinds of optimizations based on what it knew was an illegal program as a result of a call to unchecked_conversion. If the compiler does something "special" to handle a "bad" program because of unchecked_conversion, well, the conversion is not really "unchecked," right? >- Bob Matt -------------------------------------------------------------------- Matthew Heaney Software Development Consultant mheaney@ni.net (818) 985-1271