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/36947] Attributes not fully checked comparing actual vs dummy procedure
Date: Sun, 27 Jul 2008 07:24:00 -0000	[thread overview]
Message-ID: <20080727072332.22225.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36947-15045@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from burnus at gcc dot gnu dot org  2008-07-27 07:23 -------
Currently, in interface.c's compare_parameter the checking is done via
compare_interfaces. However, this function is used to check for problems with
generic interfaces and from that point of view the two procedures are not
distinguishable.

One way is to check is to add a loop as "else" branch and to check there for
INTENT and OPTIONAL of each argument. This also allows for a better error
message than the "Type/rank mismatch in argument".

If actual-argument procedure itself takes procedures as argument, one can check
recursively, which will be more work; I think for such kind of nesting no
checking is done currently.

(I thought that there was a PR already, but I cannot find it - maybe it does
not exist.)


-- 


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


  parent reply	other threads:[~2008-07-27  7:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  3:58 [Bug fortran/36947] New: accepts-invalid w6ws at earthlink dot net
2008-07-27  4:22 ` [Bug fortran/36947] Attributes not fully checked comparing actual vs dummy procedure w6ws at earthlink dot net
2008-07-27  7:24 ` burnus at gcc dot gnu dot org [this message]
2008-07-27 13:53 ` w6ws at earthlink dot net
2008-08-03  8:34 ` alex at ozo dot com
2008-08-03  8:44 ` alex at ozo dot com
2009-03-29  8:26 ` fxcoudert at gcc dot gnu dot org
2009-05-18  9:19 ` janus at gcc dot gnu dot org
2009-05-18  9:36 ` janus at gcc dot gnu dot org
2009-05-18 15:36 ` w6ws at earthlink dot net
2009-06-12 20:50 ` janus at gcc dot gnu dot org
2009-06-16  9:06 ` janus at gcc dot gnu dot org
2009-06-16  9:14 ` janus 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=20080727072332.22225.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).