public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40881]  New: warn for obsolescent features
Date: Mon, 27 Jul 2009 19:50:00 -0000	[thread overview]
Message-ID: <bug-40881-16146@http.gcc.gnu.org/bugzilla/> (raw)

gfortran should have a flag ("-Wobsolescent" or similar) to turn on warnings
about obsolescent features. These features are listed in chapter B.2 in the
Fortran standard. They are not forbidden by the standard, but are redundant and
can be replaced by newer and better features.

The standard also notes the possibility that they may be removed in the future.
Therefore gfortran should discourage their usage, just like the standard does.

Obsolescent features in Fortran 2003 are:

   (1) Arithmetic IF
   (2) Shared DO termination and termination
       on a statement other than END DO or CONTINUE
   (3) Alternate return
   (4) Computed GO TO statement
   (5) Statement functions
   (6) DATA statements amongst executable statements
   (7) Assumed length character functions
   (8) Fixed form source
   (9) CHARACTER* form of CHARACTER declaration


The -Wobsolescent flag does not have to go into -Wall (maybe -Wextra?)


-- 
           Summary: warn for obsolescent features
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: janus at gcc dot gnu dot org


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


             reply	other threads:[~2009-07-27 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 19:50 janus at gcc dot gnu dot org [this message]
2009-07-28  8:33 ` [Bug fortran/40881] " burnus at gcc dot gnu dot org
2009-07-29 11:41 ` janus at gcc dot gnu dot org
2009-07-30  8:20 ` janus at gcc dot gnu dot org
2009-08-01 14:24 ` janus at gcc dot gnu dot org
2009-08-02 10:59 ` janus at gcc dot gnu dot org
2009-08-02 11:13 ` janus at gcc dot gnu dot org
2009-08-03  7:04 ` burnus at gcc dot gnu dot org
2010-05-07 19:46 ` dfranke 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-40881-16146@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).