This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Attention GCJ devel team
- From: "Raif S. Naffah" <raif at fl dot net dot au>
- To: "Bryce McKinlay" <bryce at waitaki dot otago dot ac dot nz>,"Nic Ferrier" <nferrier at tapsellferrier dot co dot uk>
- Cc: "James Williams" <james_williams at optusnet dot com dot au>,<java at gcc dot gnu dot org>, <gcc at gcc dot gnu dot org>
- Date: Mon, 22 Apr 2002 18:27:06 +1000
- Subject: Re: Attention GCJ devel team
- References: <001e01c1e797$c91c2f30$c47831d2@computer><3CC38926.90804@waitaki.otago.ac.nz> <87znzwck4a.fsf@pooh-sticks-bridge.tapsellferrier.co.uk>
did the original poster mean when saying "generate ... from javadoc
specifications"
a. generate the code from the _output_ of the JavaDoc tool, or
b. generate the code from .java files (source code) adorned with JavaDoc
tags?
if it's the latter would that still be legally challenging?
cheers;
rsn
----- Original Message -----
From: "Nic Ferrier" <nferrier@tapsellferrier.co.uk>
To: "Bryce McKinlay" <bryce@waitaki.otago.ac.nz>
Cc: "James Williams" <james_williams@optusnet.com.au>; <java@gcc.gnu.org>;
<gcc@gcc.gnu.org>
Sent: Monday, April 22, 2002 4:39 PM
Subject: Re: Attention GCJ devel team
> Bryce McKinlay <bryce@waitaki.otago.ac.nz> 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
>
>