public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34795] inquire statement , direct= specifier incorrectly returns YES
Date: Sat, 19 Jan 2008 16:32:00 -0000	[thread overview]
Message-ID: <20080119153133.7675.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34795-15636@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from jvdelisle at gcc dot gnu dot org  2008-01-19 15:31 -------
Not that this reference is always right, but Metcalf, Reid, and Cohen state:

direct=dir where dir "... are character variables that are assigned the value
YES, NO, or UNKNOWN, depending on whether the file may be opened for ... direct
access ... or whether this can not be determined.

To me, key here is "may be opened" which implies the file is not open yet.  So,
if the file has been opened already,its nonsense to use inquire this way, but
the answer is obviously NO for a file opened for sequential.  The standard
could be improved by addressing this case where the file is already opened.
So based on that, I agree we change gfortran.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34795


  parent reply	other threads:[~2008-01-19 15:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 13:05 [Bug fortran/34795] New: " kendrick dot killian at colostate dot edu
2008-01-15 20:04 ` [Bug fortran/34795] " burnus at gcc dot gnu dot org
2008-01-16  2:34 ` kendrick dot killian at colostate dot edu
2008-01-16  4:30 ` jvdelisle at gcc dot gnu dot org
2008-01-16  7:24 ` jvdelisle at gcc dot gnu dot org
2008-01-16  7:52 ` jvdelisle at gcc dot gnu dot org
2008-01-19 16:32 ` jvdelisle at gcc dot gnu dot org [this message]
2008-01-20  8:02 ` jvdelisle at gcc dot gnu dot org
2008-01-20  8:09 ` 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=20080119153133.7675.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).