Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!think!ima!inmet!<8606040723.576@ucbvax.Berke!GOODENOUGH
From: 8606040723.576@ucbvax.Berke (GOODENOUGH@)
Newsgroups: net.lang.ada
Subject: Re: Orphaned Response
Message-ID: <-40@<8606040723.576@ucbvax.Berke>
Date: Mon, 2-Jun-86 14:29:00 EDT
Article-I.D.: <8606040.-40
Posted: Mon Jun  2 14:29:00 1986
Date-Received: Mon, 23-Jun-86 03:47:13 EDT
References: <1701997413@576@ucbvax/nerke>
Lines: 9
Nf-ID: #R:576@ucbvax/nerke:1701997413:<8606040723.576@ucbvax.Berke:-40:200:488
Nf-From: <8606040723.576@ucbvax.Berke!GOODENOUGH    Jun  2 14:29:00 1986


USE_ERROR can be raised when an attempt is made to create or open an
external file.  In particular, this exception can be raised when certain kinds
of file I/O are not supported at all by an implementation.  It can also be
argued that NAME_ERROR can be raised if no I/O operation is supported (see
14.4(1, 4, 5).  I believe that compilers for embedded targets have been
validated even though they raised NAME_ERROR or USE_ERROR when any attempt
was made to create or open a file.
-------