public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richardl at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/13800] gcj fails to compile a class that extends a class in an external lib Date: Thu, 22 Jan 2004 16:05:00 -0000 [thread overview] Message-ID: <20040122160544.8731.qmail@sources.redhat.com> (raw) In-Reply-To: <20040121210839.13800.richardl@redhat.com> ------- Additional Comments From richardl at redhat dot com 2004-01-22 16:05 ------- Upon further investigation, I discovered a workaround, namely, fully qualifying the class that you are extending e.g., public class foo extends org.apache.lucene.search.Filter { } instead of: public class foo extends Filter { } Fully qualifying the parent class name appears to always be necessary regardless of whether or not an import for that class exists. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13800
next prev parent reply other threads:[~2004-01-22 16:05 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-21 21:08 [Bug java/13800] New: " richardl at redhat dot com 2004-01-22 16:05 ` richardl at redhat dot com [this message] 2004-01-24 16:14 ` [Bug java/13800] " dhazeghi at yahoo dot com 2004-04-15 12:46 ` pinskia 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=20040122160544.8731.qmail@sources.redhat.com \ --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: linkBe 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).