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/39427] F2003: Procedures with same name as types/type constructors
Date: Thu, 30 Sep 2010 19:17:00 -0000	[thread overview]
Message-ID: <20100930191700.Etyanofq57_HycuiVokoet6nRs0gbWmQ4exUHJtPfCY@z> (raw)
In-Reply-To: <bug-39427-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #20 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-09-30 15:49:37 UTC ---
(In reply to comment #19)
> Could someone please comment on the relevance (or lack thereof) of the
> component being public in the example I submitted?

This issue was solved off list/PR. The question was how to interpret the
following, where [F2008's] R455 defines a "structure-constructor":

"C496 (R455) If derived-type-spec is a type name that is the same as a generic
name, the component-spec-list shall not be a valid actual-arg-spec-list for a
function reference that is resolvable as a generic reference to that name
(12.5.5.2)."

My interpretation is that this only disallows structure constructors, i.e.,
that generic functions have a higher precedence than structure constructors.
Thus, one can always override a constructor by a generic function. (And I do
not see how private components could alter the interpretation of C496 - even if
one reads it differently.)

F2008 also has the following note, which supports the overriding
interpretation:

"NOTE 4.58   The form 'name(...)' is interpreted as a generic
function-reference if possible; it is interpreted as a structure-constructor
only if it cannot be interpreted as a generic function-reference."


  parent reply	other threads:[~2010-09-30 15:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-39427-4@http.gcc.gnu.org/bugzilla/>
2010-09-28 23:31 ` damian at rouson dot net
2010-09-30 19:17 ` burnus at gcc dot gnu.org [this message]
2010-11-03  9:15 ` burnus at gcc dot gnu.org
2010-12-08 13:11 ` burnus at gcc dot gnu.org
2010-12-28 21:50 ` dfranke at gcc dot gnu.org
2011-01-09 22:07 ` janus at gcc dot gnu.org
2011-03-16 11:41 ` janus at gcc dot gnu.org
2011-10-11 16:17 ` burnus at gcc dot gnu.org
2011-11-09 13:56 ` burnus at gcc dot gnu.org
2011-11-16 21:58 ` burnus at gcc dot gnu.org
2011-11-16 22:28 ` burnus at gcc dot gnu.org
2011-11-17  2:29 ` damian at rouson dot net
2009-03-10 23:32 [Bug fortran/39427] New: Error on generic name equivalent to type name in same module damian at rouson dot net
2009-03-11 22:42 ` [Bug fortran/39427] F2003: Procedures with same name as types/type constructors burnus at gcc dot gnu dot org
2009-03-29  7:31 ` fxcoudert at gcc dot gnu dot org
2009-12-03 21:02 ` burnus at gcc dot gnu dot org
2010-01-23 17:25 ` janus at gcc dot gnu dot org
2010-05-04 12:10 ` steven at gcc dot gnu dot org
2010-05-04 14:25 ` damian at rouson dot net
2010-05-04 16:10 ` burnus at gcc dot gnu dot org
2010-05-04 16:13 ` burnus at gcc dot gnu dot org
2010-05-05 18:09 ` burnus at gcc dot gnu dot org
2010-05-05 18:15 ` burnus at gcc dot gnu dot org
2010-05-07  9:16 ` burnus at gcc dot gnu dot org
2010-05-07  9:20 ` burnus at gcc dot gnu dot org
2010-05-07 16:37 ` burnus at gcc dot gnu dot org
2010-05-18 21:52 ` burnus at gcc dot gnu dot org
2010-05-20 21:14 ` burnus at gcc dot gnu dot org
2010-05-25 19:55 ` burnus at gcc dot gnu dot org
2010-07-30  9:03 ` burnus at gcc dot gnu dot org
2010-07-31  2:30 ` damian at rouson dot net
2010-08-01  7:26 ` burnus 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=20100930191700.Etyanofq57_HycuiVokoet6nRs0gbWmQ4exUHJtPfCY@z \
    --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).