From: "James Williams" <james_williams@optusnet.com.au>
To: <gcc@gnu.org>
Subject: Attention GCJ devel team
Date: Fri, 19 Apr 2002 04:52:00 -0000 [thread overview]
Message-ID: <001e01c1e797$c91c2f30$c47831d2@computer> (raw)
Attention GCJ devel team
To Whom it may concern,
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.=20
Effectively this tool can generate class stubs (and automatically =
implement setters and getters, assign final variable values (using =
reflection) for the entire J2SE api in about 20 minutes. As near as I =
can tell this tool does not violate the SUN license (that I accepted =
when downloading the spec) because effectively the software does exactly =
what people would do were they implementing a clean room version of the =
api.
I am currently planning to include test writer functionality that will =
also create a testing framework (Tester for each object) and aggregated =
package Test objects used by the junit TestRunner for use in "JUNIT".
I am probably 3 weeks from finishing this.
After the Test Writer I plan on adding a code intergrator. 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. =20
I'd also be looking for feedback about other possible enhancements. The =
code generated by the tool can be released under any license that the =
person generating the code desires. Please let me know if your =
interested in evaluating the tool which I plan on releasing under the =
LGPL license.
kind regards
James Williams
next reply other threads:[~2002-04-19 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 4:52 James Williams [this message]
2002-04-21 22:01 ` Bryce McKinlay
2002-04-21 23:19 ` Nic Ferrier
2002-04-22 1:34 ` Raif S. Naffah
2002-04-23 6:23 ` Oskar Liljeblad
2002-04-23 17:12 ` 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='001e01c1e797$c91c2f30$c47831d2@computer' \
--to=james_williams@optusnet.com.au \
--cc=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).