public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ExtraLeveLInSoftware at ntlworld dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/58128] Problem using NAME (STANDARD_INPUT) in gcc-4.7.2 Date: Thu, 15 Aug 2013 19:13:00 -0000 [thread overview] Message-ID: <bug-58128-4-Fe2gkHWpLG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58128-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58128 --- Comment #4 from Ellis N. Thomas <ExtraLeveLInSoftware at ntlworld dot com> --- The decision to close this without any action seems unjustified. The problem is being rejected on the basis that the handling of the exception is faulty in the older Darwin. However, the fundamental problem is that this exception should not have been raised by OPEN (as in the cited sections of the Ada RM). Some fix to the relevant IO software is needed. The reply also states that what worked for I/O on VMS decades ago is essentially irrelevant - but regardless of whether OPEN is going to support another file being opened to Standard Input, if it doesn't it must say so by raising Name_Error or Use_Error as appropriate. In fact from the software developer's point of view it is clearly an advantage to be able to support interactive tools (like interpreters) written in Ada, and the ability to manipulate Standard Input is part of this. However, this facility itself is not the issue here. ENT/15-Aug-2013
prev parent reply other threads:[~2013-08-15 19:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-11 19:33 [Bug ada/58128] New: " ExtraLeveLInSoftware at ntlworld dot com 2013-08-14 11:59 ` [Bug ada/58128] " ExtraLeveLInSoftware at ntlworld dot com 2013-08-14 12:00 ` ExtraLeveLInSoftware at ntlworld dot com 2013-08-14 13:02 ` ebotcazou at gcc dot gnu.org 2013-08-15 19:13 ` ExtraLeveLInSoftware at ntlworld dot com [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-58128-4-Fe2gkHWpLG@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).