home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.ada
- Path: sparky!uunet!spool.mu.edu!agate!linus!linus.mitre.org!linus!mbunix!eachus
- From: eachus@oddjob.mitre.org (Robert I. Eachus)
- Subject: Re: I/O and the LRM
- In-Reply-To: jeffe@hathor.CSS.GOV's message of 17 Dec 92 13:25:00 GMT
- Message-ID: <EACHUS.92Dec17113039@oddjob.mitre.org>
- Sender: news@linus.mitre.org (News Service)
- Nntp-Posting-Host: oddjob.mitre.org
- Organization: The Mitre Corp., Bedford, MA.
- References: <206@hathor.CSS.GOV>
- Date: Thu, 17 Dec 1992 16:30:39 GMT
- Lines: 19
-
- In article <206@hathor.CSS.GOV> jeffe@hathor.CSS.GOV (Jeff Etrick) writes:
-
- > I have used the function successfully many times to get the external
- > name of a currently opened file but what I don't understand is the
- > comment about it being used in an open statement. Why would I want to use
- > this statement in an open since the file must already be opened or
- > STATUS_ERROR will be raised.
-
- Because you might want to close the file and open it again?
-
- Actually this statement is more of a direction to the implementor
- of TEXT_IO than to the user.
- --
-
- Robert I. Eachus
-
- with Standard_Disclaimer;
- use Standard_Disclaimer;
- function Message (Text: in Clever_Ideas) return Better_Ideas is...
-