public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin at mpa-garching dot mpg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28771]  New: gfortran accepts invalid variable definition
Date: Fri, 18 Aug 2006 11:39:00 -0000	[thread overview]
Message-ID: <bug-28771-2736@http.gcc.gnu.org/bugzilla/> (raw)

As far as I know, the following code snippet is not valid Fortran:

program test
  character(len=*) :: foo = 'test'
end

To make the code correct, the variable definition either needs the "parameter"
attribute or an explicit length.
Other compilers (Intel, Fujitsu and NAG) reject this code, but all current
versions of gfortran accept it without warning.


-- 
           Summary: gfortran accepts invalid variable definition
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: martin at mpa-garching dot mpg dot de
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2006-08-18 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 11:39 martin at mpa-garching dot mpg dot de [this message]
2006-08-18 18:20 ` [Bug fortran/28771] " patchapp at dberlin dot org
2006-08-18 18:29 ` pault at gcc dot gnu dot org
2006-08-20  5:47 ` pault at gcc dot gnu dot org
2006-08-20  8:21 ` pault at gcc dot gnu dot org
2006-08-20 18:09 ` pault at gcc dot gnu dot org
2006-08-24  4:47 ` pault at gcc dot gnu dot org
2006-08-24  4:54 ` pault 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-28771-2736@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).