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/39997] Procedure(), pointer  & implicit typing: rejects-valid / accepts-invalid?
Date: Sun, 16 Aug 2009 12:21:00 -0000	[thread overview]
Message-ID: <20090816122112.11579.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39997-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from burnus at gcc dot gnu dot org  2009-08-16 12:21 -------
Tracking of the remaining items:

a) Implicit typing of external procedures in general: I filled PR 41083 for
this purpose.

b) Implicit typing of procedure components:

   "procedure pointer components are never implicitly typed.  The
    quoted text from the standard does not apply to components; if it
    did apply to components, data components would also be implicitly
    typed and that would be a contradiction.  A clarifying edit is
    provided."

Quoted answer from interpretation request F03/0134 (09-236).
See http://www.j3-fortran.org/doc/year/09/09-236r1.txt

I understand this such that

  type t
    procedure(), pointer :: ptr
  end type t

is a ptr to a subroutine as it cannot be implicitly typed and thus cannot be a
function. The following program is invalid (quote from the interpretation
request) but accepted by gfortran:

  PROGRAM implicitppc
    EXTERNAL proc
    TYPE t
      PROCEDURE(),POINTER,NOPASS :: ptr
    END TYPE t
    TYPE(t) :: i
    i%ptr => proc
    PRINT *,i%ptr()
  END PROGRAM


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-08-16 12:21:12
               date|                            |


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


  parent reply	other threads:[~2009-08-16 12:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 20:25 [Bug fortran/39997] New: " burnus at gcc dot gnu dot org
2009-05-04  7:12 ` [Bug fortran/39997] " burnus at gcc dot gnu dot org
2009-05-11 22:56 ` burnus at gcc dot gnu dot org
2009-05-15 10:32 ` burnus at gcc dot gnu dot org
2009-06-24 12:59 ` burnus at gcc dot gnu dot org
2009-06-24 21:53 ` burnus at gcc dot gnu dot org
2009-06-26 22:11 ` janus at gcc dot gnu dot org
2009-08-16 12:21 ` burnus at gcc dot gnu dot org [this message]
2009-11-16 20:53 ` burnus at gcc dot gnu dot org
2009-11-24  8:28 ` janus at gcc dot gnu dot org
2010-04-06 16:26 ` burnus at gcc dot gnu dot org
2010-04-06 16:37 ` burnus at gcc dot gnu dot org
     [not found] <bug-39997-4@http.gcc.gnu.org/bugzilla/>
2013-12-11 11:50 ` janus 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=20090816122112.11579.qmail@sourceware.org \
    --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).