public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45271] [OOP] Polymorphic code breaks when changing order of USE statements
Date: Fri, 13 Aug 2010 09:50:00 -0000	[thread overview]
Message-ID: <20100813095000.12266.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45271-6318@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from janus at gcc dot gnu dot org  2010-08-13 09:50 -------
The problem is the following:

We have two routines called 'my_assign' (in two different modules). When
initializing the vtabs in the main program, we happen to use the wrong one:

      if (vtab$trivial_gradient_type.assign == 0B)
        {
          vtab$trivial_gradient_type.assign = my_assign;
        }


Possible solutions:
1) Make sure we use the right symbol from the right module.
2) Do the vtab initialization inside the module that defines the class, i.e.
add a module procedure like 'vtab$trivial_gradient_type$init' which does it,
and call this from the main program. Then there is no name ambiguity.


-- 


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


  parent reply	other threads:[~2010-08-13  9:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 19:55 [Bug fortran/45271] New: " anlauf at gmx dot de
2010-08-12 19:56 ` [Bug fortran/45271] " anlauf at gmx dot de
2010-08-13  8:22 ` janus at gcc dot gnu dot org
2010-08-13  9:30 ` janus at gcc dot gnu dot org
2010-08-13  9:50 ` janus at gcc dot gnu dot org [this message]
2010-08-13 12:36 ` janus at gcc dot gnu dot org
2010-08-13 14:25 ` mikael at gcc dot gnu dot org
2010-08-13 14:31 ` janus at gcc dot gnu dot org
2010-08-13 17:23 ` janus at gcc dot gnu dot org
2010-08-15 20:01 ` janus at gcc dot gnu dot org
2010-08-19 13:09 ` janus at gcc dot gnu dot org
2010-08-21 14:51 ` janus at gcc dot gnu dot org
2010-08-21 15:00 ` 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=20100813095000.12266.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).