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/36895] New: Namelist writting to internal files: Control characters wrong?
Date: Tue, 22 Jul 2008 07:00:00 -0000 [thread overview]
Message-ID: <bug-36895-13404@http.gcc.gnu.org/bugzilla/> (raw)
Found at
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/543dbbd5a3cb5fce
Jerry, could you check whether Richard Maine's concerns are correct or not? NAG
f95 and g95 write everything in one line; g95 has also a trailing comma, NAG
does not. (ifort 11beta and sunf95 don't support nml for internal files, yet.)
For external files, g95 prints a newline before "/". (ifort and sunf95 print
also in several lines, but without trailing comma.)
----------------- Richard Maine writes: ------------------------------
> C:\gcc_mingw64a\clf\nakelist>nakelist
> &STUFF
> N= 666, /
That output showed up in the posting as being on two lines (at least in
my newsreader). I hope that was an artifact of the newsgroup posting. If
the compiler actually does something like put control characters (such
as cr and/or lf) in the internal file, then that would be a bug.
Also, the comma looks wrong to me. I don't think it is allowed. I
suppose I'd need to study more carefully to be 100% sure, but the comma
is a separator - not a terminator. That also looks like a bug, and one
less likely to be a posting artifact.
--
Summary: Namelist writting to internal files: Control characters
wrong?
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36895
next reply other threads:[~2008-07-22 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 7:00 burnus at gcc dot gnu dot org [this message]
2008-07-22 9:02 ` [Bug fortran/36895] " burnus at gcc dot gnu dot org
2008-07-22 16:48 ` jvdelisle at gcc dot gnu dot org
2008-07-22 17:48 ` burnus at gcc dot gnu dot org
2008-07-23 1:40 ` jvdelisle at gcc dot gnu dot org
2008-08-31 0:07 ` jvdelisle at gcc dot gnu dot org
2008-08-31 0:10 ` jvdelisle at gcc dot gnu dot org
2008-08-31 0:15 ` 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-36895-13404@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: 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).