From: "Raif S. Naffah" <raif@fl.net.au>
To: "Bryce McKinlay" <bryce@waitaki.otago.ac.nz>,
"Nic Ferrier" <nferrier@tapsellferrier.co.uk>
Cc: "James Williams" <james_williams@optusnet.com.au>,
<java@gcc.gnu.org>, <gcc@gcc.gnu.org>
Subject: Re: Attention GCJ devel team
Date: Mon, 22 Apr 2002 01:34:00 -0000 [thread overview]
Message-ID: <000d01c1e9d7$7e30eaa0$1902b5ca@solomon> (raw)
In-Reply-To: <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
>
>
next prev parent reply other threads:[~2002-04-22 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 4:52 James Williams
2002-04-21 22:01 ` Bryce McKinlay
2002-04-21 23:19 ` Nic Ferrier
2002-04-22 1:34 ` Raif S. Naffah [this message]
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='000d01c1e9d7$7e30eaa0$1902b5ca@solomon' \
--to=raif@fl.net.au \
--cc=bryce@waitaki.otago.ac.nz \
--cc=gcc@gcc.gnu.org \
--cc=james_williams@optusnet.com.au \
--cc=java@gcc.gnu.org \
--cc=nferrier@tapsellferrier.co.uk \
/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).