public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: "James Williams" <james_williams@optusnet.com.au>
To: "Bryce McKinlay" <bryce@waitaki.otago.ac.nz>,
	"Nic Ferrier" <nferrier@tapsellferrier.co.uk>
Cc: <java@gcc.gnu.org>, <gcc@gcc.gnu.org>
Subject: Re: Attention GCJ devel team
Date: Mon, 22 Apr 2002 01:27:00 -0000	[thread overview]
Message-ID: <001901c1e9ce$6705e960$23138ec6@computer> (raw)
In-Reply-To: <87znzwck4a.fsf@pooh-sticks-bridge.tapsellferrier.co.uk>

Whether to generate the javadoc or not is an option that the user can set at
the time of generation.

The cool thing about generating the javadoc is that it updates whether or
not the method,class etc is deprecated.  This is why I'm having trouble with
the whole "javadoc is copyrighted" issue because deprecation is part of the
specification and part of the javadoc.

Either way I will be forwarding the finished source to you guys for eval and
if you find it useful then please feel free to use and contribute to it.

Thanks for the reply
James


----- 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
>

  reply	other threads:[~2002-04-22  7:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001e01c1e797$c91c2f30$c47831d2@computer>
2002-04-21 22:22 ` Bryce McKinlay
2002-04-22  0:22   ` Nic Ferrier
2002-04-22  1:27     ` James Williams [this message]
2002-04-22 11:03     ` Raif S. Naffah
2002-04-23  7:25   ` Oskar Liljeblad
2002-04-23 18:04     ` Bryce McKinlay
2002-04-23 22:29 James Williams
2002-04-23 22:42 ` 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='001901c1e9ce$6705e960$23138ec6@computer' \
    --to=james_williams@optusnet.com.au \
    --cc=bryce@waitaki.otago.ac.nz \
    --cc=gcc@gcc.gnu.org \
    --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).