public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "david at jpackage dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/26390] New: Problem dispatching method call when method does not exist in superclass
Date: Tue, 21 Feb 2006 08:32:00 -0000 [thread overview]
Message-ID: <bug-26390-11339@http.gcc.gnu.org/bugzilla/> (raw)
Classpath 0.21-pre contains the following code in
gnu/java/awt/peer/swing/SwingFramePeer.java:
public void setBounds(int x, int y, int w, int h)
{
super.setBounds(x, y, w, h);
if (menuBar != null)
menuBar.setWidth(w);
where the method setBounds(int, int, int, int) does not exist in the immediate
superclass (SwingWindowPeer). The class appears to compile, but during the
linking phase we get undefined reference to
java::awt::peer::swing::SwingWindowPeer::setBounds(int, int, int, int).
--
Summary: Problem dispatching method call when method does not
exist in superclass
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: david at jpackage dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26390
next reply other threads:[~2006-02-21 8:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 8:32 david at jpackage dot org [this message]
2006-02-22 14:31 ` [Bug java/26390] " pinskia at gcc dot gnu dot org
2006-03-09 3:16 ` mckinlay at redhat dot com
2006-03-10 18:13 ` mark at gcc dot gnu dot org
2006-03-10 23:00 ` tromey at gcc dot gnu dot org
2006-03-11 1:40 ` tromey at gcc dot gnu dot org
2006-03-13 17:10 ` tromey at gcc dot gnu dot org
2006-03-13 17:12 ` tromey at gcc dot gnu dot org
2006-03-13 19:07 ` tromey at gcc dot gnu dot org
2006-03-15 18:29 ` tromey at gcc dot gnu dot org
2006-03-15 18:31 ` tromey at gcc dot gnu dot org
2006-03-29 16:32 ` tromey at gcc dot gnu dot org
2006-03-29 16:36 ` tromey at gcc dot gnu dot org
2006-12-28 15:45 ` rob1weld at aol dot com
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-26390-11339@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).