From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20825 invoked by alias); 19 Apr 2002 11:45:24 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 20790 invoked from network); 19 Apr 2002 11:45:16 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sources.redhat.com with SMTP; 19 Apr 2002 11:45:16 -0000 Received: from mail017.syd.optusnet.com.au ([210.49.20.175]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16yWpG-0001qS-00 for ; Fri, 19 Apr 2002 07:45:14 -0400 Received: from computer (wdcax21-196.dialup.optusnet.com.au [210.49.120.196]) by mail017.syd.optusnet.com.au (8.11.1/8.11.1) with SMTP id g3JBjAl28541 for ; Fri, 19 Apr 2002 21:45:10 +1000 Message-ID: <001e01c1e797$c91c2f30$c47831d2@computer> From: "James Williams" To: Subject: Attention GCJ devel team Date: Fri, 19 Apr 2002 04:52:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-SW-Source: 2002-04/txt/msg00932.txt.bz2 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