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] Namelist writting to internal files:  Control characters wrong?
Date: Tue, 22 Jul 2008 17:48:00 -0000	[thread overview]
Message-ID: <20080722174718.17070.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36895-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from burnus at gcc dot gnu dot org  2008-07-22 17:47 -------
> I will check on this later tonight or this week.  I have wondered about that
> comma myself.

Thanks! I believe the comma should be valid, even though it is superfluous and
"looks wrong". Thus it were nice if one could get rid of it, but only if it is
not too much work and does not slow down the I/O.

Regarding the line breaks: I think they are indeed wrong. At the moment I
cannot come up with a good example how this can cause problems, but I'm sure
one could construct one.

Running the following program using NAG f95 gives the error:
Invalid character '
' in NAMELIST input
Program terminated by I/O error on internal file

Thus NAG f95 does not like the line break. (The program works in g95 and
gfortran.)

----------------------
character(len=255) :: str(2)
integer :: i, j(2)
namelist /nm/i,j
i = 44
j = 45
str(1) = ' &NM '//new_line('a')//' I=          1,'
str(2) = ' J= 2*2          ,  /'
read(str,nml=nm)
print *, i, j
end
----------------------


-- 


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


  parent reply	other threads:[~2008-07-22 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22  7:00 [Bug fortran/36895] New: " burnus at gcc dot gnu dot org
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 [this message]
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=20080722174718.17070.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).