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/29835]  New: Error message of non-unknown edit descriptor needs improvement
Date: Tue, 14 Nov 2006 18:01:00 -0000	[thread overview]
Message-ID: <bug-29835-13404@http.gcc.gnu.org/bugzilla/> (raw)

gfortran writes:
    read(1,'(Q,A)',iostat=i) n,line(:n)
                                      1
Warning: Unexpected element in format string at (1)

And if there is a long comment it may even look like:
XLINE
    1
Warning: Unexpected element in format string at (1)


Expected:
    read(1,'(Q,A)',iostat=i) n,line(:n)
             1
Warning: Unexpected element in format string at (1)
or even:
Warning: Unexpected element 'Q' in format string at (1)

(The run-time message is also slightly misaligned:
read(1,'(Q,A)') n,line(:n)
       1

---------- Test program ---------
integer, parameter :: MAXLINE = 255
character(MAXLINE) line
open(1,file='whatever', access='sequential',form='formatted',action='read')
do
   read(1,'(Q,A)',iostat=i) n,line(:n)
   if (i/=0) exit
! real work here
 enddo
end
---------- Test program ---------
Cf.
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/d968667b1e3219ab

 * * *

The Q edit descriptor is, e.g., described at
http://www.helsinki.fi/atk/unix/dec_manuals/cf77au/olrm0242.htm

It is documented but not supported in g77, seems to be a DEC extension and is
supported by ifort and sunf95.
I think, gfortran does not need to support it.


-- 
           Summary: Error message of non-unknown edit descriptor needs
                    improvement
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          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=29835


             reply	other threads:[~2006-11-14 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 18:01 burnus at gcc dot gnu dot org [this message]
2006-11-14 18:01 ` [Bug fortran/29835] " burnus at gcc dot gnu dot org
2007-01-02  4:51 ` [Bug fortran/29835] Error message of unknown " jvdelisle at gcc dot gnu dot org
2007-09-08 20:16 ` jvdelisle at gcc dot gnu dot org
2008-07-22 17:07 ` domob at gcc dot gnu dot org
2008-07-22 17:11 ` domob 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-29835-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).