public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jkrahn at nc dot rr dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/44931] New: For INPUT_UNIT, INQUIRE NAME= should not return "stdin" Date: Tue, 13 Jul 2010 20:51:00 -0000 [thread overview] Message-ID: <bug-44931-14229@http.gcc.gnu.org/bugzilla/> (raw) The F2003 spec has the following not about the NAME= specifier: -------- NOTE 9.63 If this specifier appears in an INQUIRE by file statement, its value is not necessarily the same as the name given in the FILE= specifier. However, the value returned shall be suitable for use as the value of the file-name-expr in the FILE= specifier in an OPEN statement. The processor may return a file name qualified by a user identification, device, directory, or other relevant information. -------- The second part of the note suggests that a dummy name like "stdin" may be acceptable, but it does not conform to the first part of the note. OPEN will accept "stdin" as a normal filename. The easiest implementation is to return the actual stdin device name. Otherwise, just leave it unnamed. Obviously, the same is true of standard output and error units. -- Summary: For INPUT_UNIT, INQUIRE NAME= should not return "stdin" Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jkrahn at nc dot rr dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44931
next reply other threads:[~2010-07-13 20:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-13 20:51 jkrahn at nc dot rr dot com [this message] 2010-07-14 15:44 ` [Bug fortran/44931] " burnus at gcc dot gnu dot org 2010-07-15 21:39 ` jkrahn at nc dot rr dot com 2010-07-15 21:49 ` jkrahn at nc dot rr dot com 2010-07-24 4:08 ` jvdelisle at gcc dot gnu dot org 2010-07-24 8:22 ` burnus at gcc dot gnu dot org 2010-07-25 0:48 ` jvdelisle at gcc dot gnu dot org 2010-07-29 1:32 ` jvdelisle at gcc dot gnu dot org 2010-07-29 8:26 ` burnus at gcc dot gnu dot org 2010-07-30 1:47 ` jvdelisle at gcc dot gnu dot org 2010-08-04 10:02 ` burnus at gcc dot gnu dot org 2010-08-14 18:59 ` jvdelisle at gcc dot gnu dot org 2010-08-17 3:14 ` jvdelisle at gcc dot gnu dot org
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-44931-14229@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).