public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vivekrao4 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30681]  New: "obsolescent" vs. "obsolete"
Date: Fri, 02 Feb 2007 15:27:00 -0000	[thread overview]
Message-ID: <bug-30681-9647@http.gcc.gnu.org/bugzilla/> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]

For a code with an arithmetic IF, for example

program xx
implicit none
integer :: i
i = 0
if (i) 10,20,30
10 print*,"negative"
stop
20 print*,"zero"
stop
30 print*,"positive"
stop
end program xx

mingw gfortran 4.3.0 20061021 says

 In file xarithmetic_if.f90:5

if (i) 10,20,30
              1
Warning: Obsolete: arithmetic IF statement at (1)

According to the Fortran 95 Handbook the arithmetic IF is "obsolescent", not
"obsolete".

The Fortran 2003 standard lists the following features as "obsolescent" in
section B.2, "Obsolescent features".

5 (1) Arithmetic IF — use the IF statement (8.1.2.4) or IF construct (8.1.2).
6 (2) Shared DO termination and termination on a statement other than END DO or
CON7
TINUE — use an END DO or a CONTINUE statement for each DO statement.
8 (3) Alternate return — see B.2.1.
9 (4) Computed GO TO statement — see B.2.2.
10 (5) Statement functions — see B.2.3.
11 (6) DATA statements amongst executable statements — see B.2.4.
12 (7) Assumed length character functions — see B.2.5.
13 (8) Fixed form source — see B.2.6.
14 (9) CHARACTER* form of CHARACTER declaration — see B.2.7.

Gfortran should use the term "obsolescent" rather than "obsolete" for all of
these features. I have only looked at arithmetic IF.


-- 
           Summary: "obsolescent" vs. "obsolete"
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: vivekrao4 at yahoo dot com


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


             reply	other threads:[~2007-02-02 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 15:27 vivekrao4 at yahoo dot com [this message]
2007-02-05 14:05 ` [Bug fortran/30681] " vivekrao4 at yahoo dot com
2007-02-05 16:25 ` kargl at gcc dot gnu dot org
2007-02-07  2:11 ` jvdelisle at gcc dot gnu dot org
2007-02-07  4:31 ` patchapp at dberlin dot org
2007-02-19  6:30 ` patchapp at dberlin dot org
2007-02-19  6:48 ` jvdelisle at gcc dot gnu dot org
2007-02-19  6:52 ` jvdelisle at gcc dot gnu dot org
2007-02-23 18:17 ` jvdelisle at gcc dot gnu dot org
2007-02-23 18:20 ` jvdelisle at gcc dot gnu dot org
2007-02-23 18:37 ` 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=bug-30681-9647@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).