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/56500] [OOP] "IMPLICIT CLASS(...)" wrongly rejected
Date: Sat, 02 Mar 2013 00:07:00 -0000	[thread overview]
Message-ID: <bug-56500-4-ZUuZFifw88@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56500-4@http.gcc.gnu.org/bugzilla/>


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

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

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

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-02 00:06:45 UTC ---
The problem seems to be that "class_ok" is not true; the reason seems to be
that gfc_build_class_symbol does not get called.

I am not sure, when it has to be called but it currently fails for:

  implicit class(*) (a-z)
  allocatable :: foo
  end
and for
  subroutine foo(x)
  implicit class(*) (a-z)
  end

The error message is printed in resolve.c's resolve_fl_var_and_proc:

  /* Constraints on polymorphic variables.  */
...
      if (!sym->attr.class_ok && !sym->attr.use_assoc && !sym->assoc)
        {
          gfc_error ("CLASS variable '%s' at %L must be dummy, allocatable "
                     "or pointer", sym->name, &sym->declared_at);


gfc_build_class_symbol is currently only called in decl.c via "build_struct"
and via attr_decl1. One probably has to call it in symbol.c's 
gfc_set_default_type


  reply	other threads:[~2013-03-02  0:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 18:07 [Bug fortran/56500] New: " burnus at gcc dot gnu.org
2013-03-02  0:07 ` burnus at gcc dot gnu.org [this message]
2013-03-17 12:55 ` [Bug fortran/56500] " janus at gcc dot gnu.org
2013-03-17 13:12 ` janus at gcc dot gnu.org
2013-03-17 16:00 ` janus at gcc dot gnu.org
2013-03-17 19:46 ` dominiq at lps dot ens.fr
2013-03-17 21:02 ` janus at gcc dot gnu.org
2013-03-17 21:30 ` dominiq at lps dot ens.fr
2013-03-17 22:38 ` janus at gcc dot gnu.org
2013-03-18 12:17 ` dominiq at lps dot ens.fr
2013-03-18 12:57 ` janus at gcc dot gnu.org
2013-04-01 15:34 ` 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=bug-56500-4-ZUuZFifw88@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).