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,549562583b1942d9
X-Google-Attributes: gid103376,public
From: "Bernd Ragutt" <BerndRagutt@csi.com>
Subject: Re: exceptions and streams
Date: 1998/11/02
Message-ID: <#CgYVsiB#GA.338@nih2naaa.prod2.compuserve.com>#1/1
X-Deja-AN: 407476907
References: <O8CzNTFB#GA.364@nih2naaa.prod2.compuserve.com>
 <71fodt$r3u$1@nnrp1.dejanews.com>
Newsgroups: comp.lang.ada
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Date: 1998-11-02T00:00:00+00:00
List-Id: <comp.lang.ada>

dewarr@my-dejanews.com wrote:
>I don't know why you think there is a contradiction here. There is most
>certainly a requirement that you can write exception occurrences to a
stream,
>and this is quite an important capability.


RM 11.4.1 (16) requires the existence of a Wrtite atrribute:

    "The implementation of the Write attribute (see 13.13.2) of
    Exception_Occurrence shall support writing a representation of an
    exception occurrence to a stream"


whereas RM 13.13.2 (36) states that the use is illegal for
limited types:

    "All nonlimited types have default implementations
    for these operations [stream-oriented attributes ].
    An attribute_reference for one of these attributes is
    illegal if the type is limited, unless the attribute has
    been specified by an attribute_definition_clause."



Bernd
----------------------
BerndRagutt@csi.com