From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: James Williams <james_williams@optusnet.com.au>
Cc: java@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Attention GCJ devel team
Date: Sun, 21 Apr 2002 22:22:00 -0000 [thread overview]
Message-ID: <3CC38926.90804@waitaki.otago.ac.nz> (raw)
In-Reply-To: <001e01c1e797$c91c2f30$c47831d2@computer>
James Williams wrote:
>I am currently working on a tool that will generate class stubs complete
>with javadoc from javadoc specifications. In your FAQ a person
>mentioned that "Considering that new Java APIs come out every week, it's
>going to be impossible to track everything." I believe the tool I am
>developing may reduce this development challenge for you substantially.
>
From my perspective the value of this would be that when a new specification
>came out, the api converter could be run providing a clean framework
>complete with all the new and deprecated api's and then the intergrator
>could copy the existing code from the current libgcj implementation into
>the new framework.
>
This sounds like an interesting and useful tool. However, I don't know
whether or not we can, from a legal perspective, generate code
directly/automatically from Javadocs. I suspect we'd have to ask the FSF
legal people whether or not this is safe.
regards
Bryce.
next parent reply other threads:[~2002-04-22 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001e01c1e797$c91c2f30$c47831d2@computer>
2002-04-21 22:22 ` Bryce McKinlay [this message]
2002-04-22 0:22 ` Nic Ferrier
2002-04-22 1:27 ` James Williams
2002-04-22 11:03 ` Raif S. Naffah
2002-04-23 7:25 ` Oskar Liljeblad
2002-04-23 18:04 ` Bryce McKinlay
2002-04-23 22:29 James Williams
2002-04-23 22:42 ` Bryce McKinlay
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=3CC38926.90804@waitaki.otago.ac.nz \
--to=bryce@waitaki.otago.ac.nz \
--cc=gcc@gcc.gnu.org \
--cc=james_williams@optusnet.com.au \
--cc=java@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).