From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11274 invoked by alias); 22 Apr 2002 06:17:35 -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 11139 invoked from network); 22 Apr 2002 06:17:31 -0000 Received: from unknown (HELO tf1.tapsellferrier.co.uk) (217.34.135.17) by sources.redhat.com with SMTP; 22 Apr 2002 06:17:31 -0000 Received: from host217-34-135-21.in-addr.btopenworld.com ([217.34.135.21] helo=pooh-sticks-bridge.tapsellferrier.co.uk) by tf1.tapsellferrier.co.uk with esmtp (Exim 3.35 #1 (Debian)) id 16zXZB-0006h0-00; Mon, 22 Apr 2002 07:44:49 +0100 To: Bryce McKinlay Cc: James Williams , java@gcc.gnu.org, gcc@gcc.gnu.org Subject: Re: Attention GCJ devel team References: <001e01c1e797$c91c2f30$c47831d2@computer> <3CC38926.90804@waitaki.otago.ac.nz> From: Nic Ferrier Date: Sun, 21 Apr 2002 23:19:00 -0000 In-Reply-To: <3CC38926.90804@waitaki.otago.ac.nz> Message-ID: <87znzwck4a.fsf@pooh-sticks-bridge.tapsellferrier.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-04/txt/msg01064.txt.bz2 Bryce McKinlay writes: > 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. We had the same issue with ClasspathX and I think the result was that it's not legal (sun have (c) on the javadoc produced text). But I don't have any copy of an FSF mail so you may as well ask again. However, such a tool would still be useful, just as a monitoring tool. Nic