public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/5365: gcjh -stubs does not include correct files Date: Wed, 16 Jan 2002 13:16:00 -0000 [thread overview] Message-ID: <20020116211605.23305.qmail@sources.redhat.com> (raw) The following reply was made to PR java/5365; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: nicholas allen <nicholas.allen@ireland.sun.com> Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/5365: gcjh -stubs does not include correct files Date: 16 Jan 2002 14:26:46 -0700 >>>>> "Nicholas" == nicholas allen <nicholas.allen@ireland.sun.com> writes: Nicholas> I like the idea of thowing an exception (say Nicholas> java.lang.UnsupportedOperationException("Method not Nicholas> implemented yet")). I know this would require include the Nicholas> header file for the exception but this can always be deleted Nicholas> and causes no harm if left in. I agree. I'm making this change. Nicholas> It would also be nice if gcjh -stubs didn't generate a stub Nicholas> file if there were no native methods in the class file. This would be nice but it is hard to implement given the current code. Feel free to submit another PR for this if you like. Please make it low priority. Nicholas> Another idea would be too ask (or warn) the user if a file Nicholas> already exists before overwiting it with the stub file. This Nicholas> would prevent loosing implementations that have already been Nicholas> written by mistake. This would also be nice, and it worth another low priority PR... or a patch. Thanks, Tom
next reply other threads:[~2002-01-16 21:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-16 13:16 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-16 13:19 tromey 2002-01-15 16:26 Tom Tromey 2002-01-12 12:46 nallen
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=20020116211605.23305.qmail@sources.redhat.com \ --to=tromey@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).