public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52101] Obsolescence warning for non-obs. feature character name*length
Date: Fri, 03 Feb 2012 07:22:00 -0000	[thread overview]
Message-ID: <bug-52101-4-rEXvf2AvNE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52101-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |burnus at gcc dot gnu.org
         Resolution|                            |INVALID

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-02-03 07:22:28 UTC ---
(In reply to comment #0)
> Gfortran 4.6.2 -std=f95 says a declaration character name*length is
> obsolescent. IMHO it is not; the obsolescent form is character*length name.
> 
> character greet*11
>                   1
> Warning: Obsolescent feature: Old-style character length at (1)

See Fortran 95 standard,
  http://gcc.gnu.org/wiki/GFortranStandards
  http://j3-fortran.org/doc/standing/archive/007/97-007r2/pdf/97-007r2.pdf
in Section "B.2 Obsolescent features":

"The obsolescent features are those features of Fortran 90 that were redundant
and for which better methods were available in Fortran 90. Section 1.7.2
describes the nature of the obsolescent features. The obsolescent features in
this standard are the following:
...
(9) CHARACTER* form of CHARACTER declaration - see B.2.7."


Closed as INVALID.


  reply	other threads:[~2012-02-03  7:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03  0:11 [Bug fortran/52101] New: " john.harper at vuw dot ac.nz
2012-02-03  7:22 ` burnus at gcc dot gnu.org [this message]
2012-02-03  7:31 ` [Bug fortran/52101] " burnus at gcc dot gnu.org
2012-02-03 20:51 ` John.Harper at msor dot vuw.ac.nz
2012-02-03 21:17 ` kargl at gcc dot gnu.org
2012-02-03 22:48 ` sgk at troutmask dot apl.washington.edu
2012-02-04  0:01 ` sgk at troutmask dot apl.washington.edu
2012-02-05  9:59 ` burnus at gcc dot gnu.org
2012-02-05 18:01 ` sgk at troutmask dot apl.washington.edu
2012-02-05 18:12 ` burnus at gcc dot gnu.org
2012-07-16 19:38 ` burnus at gcc dot gnu.org
2012-07-17  9:40 ` burnus at gcc dot gnu.org
2012-07-17 11:28 ` burnus at gcc dot gnu.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-52101-4-rEXvf2AvNE@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).