public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "jbarnett at 2wire dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/16658] errors compiling saxon xslt library Date: Wed, 21 Jul 2004 17:57:00 -0000 [thread overview] Message-ID: <20040721175728.15409.qmail@sourceware.org> (raw) In-Reply-To: <20040721172610.16658.jbarnett@2wire.com> ------- Additional Comments From jbarnett at 2wire dot com 2004-07-21 17:57 ------- Clarification: for the AbstractNode.java problem, it's not actually all the classes in the com.icl.saxon.om package that fail, just the ones that implement the "Node, NodeInfo, SourceLocator, DOMLocator" interfaces. The common class definition that fails is: public abstract class XXX implements Node, NodeInfo, SourceLocator, DOMLocator { ... } files that succeed either do not inherit or implement classes, or are classes taht extend Exception, or interfaces that exetend NodeInfo -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16658
next prev parent reply other threads:[~2004-07-21 17:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-21 17:26 [Bug java/16658] New: " jbarnett at 2wire dot com 2004-07-21 17:57 ` jbarnett at 2wire dot com [this message] 2004-07-22 17:01 ` [Bug java/16658] " jbarnett at 2wire dot com 2004-09-08 21:50 ` jbarnett at 2wire dot com 2004-09-08 22:45 ` tromey at gcc dot gnu dot org 2004-09-08 23:28 ` jbarnett at 2wire dot com 2004-09-08 23:57 ` tromey at gcc dot gnu dot org 2004-09-09 0:01 ` jbarnett at 2wire dot com 2004-09-09 14:48 ` tromey at gcc dot gnu dot org 2004-09-09 16:38 ` pinskia at gcc dot gnu dot org 2004-10-15 17:16 ` jbarnett at 2wire dot com [not found] <bug-16658-8989@http.gcc.gnu.org/bugzilla/> 2007-01-09 20:48 ` tromey 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=20040721175728.15409.qmail@sourceware.org \ --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: 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).