public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/39072] I/O READing logical value beyond end of string
Date: Sun, 01 Feb 2009 23:18:00 -0000	[thread overview]
Message-ID: <20090201231823.9628.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39072-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from burnus at gcc dot gnu dot org  2009-02-01 23:18 -------
If one reads an integer ("i1") instead of a logical variable ("l1"),
gfortran/g95/f95 read a "0".

 * * *

"10.6.2 Logical editing" makes it quite explicit that it is invalid:

"The input field consists of optional blanks, optionally followed by a period,
followed by a T for true or F for false. The T or F may be followed by
additional characters in the field, which are ignored. A lower-case letter is
equivalent to the corresponding upper-case letter in a logical input field."

Regarding "i1":
"10.6.1 Numeric editing": "On input, [...] A field containing only blanks is
considered to be zero."


-- 


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


  parent reply	other threads:[~2009-02-01 23:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 23:08 [Bug fortran/39072] New: " burnus at gcc dot gnu dot org
2009-02-01 23:09 ` [Bug fortran/39072] " burnus at gcc dot gnu dot org
2009-02-01 23:18 ` burnus at gcc dot gnu dot org [this message]
2009-02-03  4:43 ` jvdelisle at gcc dot gnu dot org
2009-02-03 10:02 ` burnus at gcc dot gnu dot org
2009-02-04  1:55 ` 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=20090201231823.9628.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).