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] For INPUT_UNIT, INQUIRE NAME= should not return "stdin"
Date: Thu, 15 Jul 2010 21:49:00 -0000 [thread overview]
Message-ID: <20100715214947.31661.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44931-14229@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from jkrahn at nc dot rr dot com 2010-07-15 21:49 -------
I noticed that Fedora now include symlinks for /dev/stdin, /dev/stdout,
/dev/stderr. It would be reasonable to use those path names if there is an
interest in avoiding blank names. This convention may not hold on all
platforms, but those device names probably will not exist otherwise.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44931
next prev parent reply other threads:[~2010-07-15 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:51 [Bug fortran/44931] New: " jkrahn at nc dot rr dot com
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 [this message]
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
[not found] <bug-44931-4@http.gcc.gnu.org/bugzilla/>
2010-11-04 19:30 ` jb at gcc dot gnu.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=20100715214947.31661.qmail@sourceware.org \
--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: link
Be 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).