public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: Oskar Liljeblad <oskar@osk.mine.nu>
Cc: James Williams <james_williams@optusnet.com.au>,
	java@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Attention GCJ devel team
Date: Tue, 23 Apr 2002 17:12:00 -0000	[thread overview]
Message-ID: <3CC5F4DB.1070603@waitaki.otago.ac.nz> (raw)
In-Reply-To: <20020423124246.GA24351@oskar>

Oskar Liljeblad wrote:

>I wrote a program similar to what you describe some time ago. It is called
>DeDoc and can be downloaded from
>http://freshmeat.net/redir/dedoc/1802/url_tgz/dedoc-0.12.tar.gz.
>It reads HTML (generated by javadoc from java source files) and writes
>source files for each class encountered. I don't know if anyone actually
>uses/used it...
>
>The same question came up that time - is it legal to use code automaticly
>generated from Javadoc [in GPL programs]? I wrote RMS to ask about it,
>and he forwarded my email to Eben Moglen. I quote from the letters I
>received:
>

Thanks Oskar. I believe we can conclude from this that it is ok to use 
automated tools to generate templates for implementing classes from 
Javadocs, provided that it is only the member names and signatures that 
are being copied and not the documentation itself.

regards

Bryce.



      reply	other threads:[~2002-04-23 23:59 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
2002-04-23  6:23   ` Oskar Liljeblad
2002-04-23 17:12     ` Bryce McKinlay [this message]

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=3CC5F4DB.1070603@waitaki.otago.ac.nz \
    --to=bryce@waitaki.otago.ac.nz \
    --cc=gcc@gcc.gnu.org \
    --cc=james_williams@optusnet.com.au \
    --cc=java@gcc.gnu.org \
    --cc=oskar@osk.mine.nu \
    /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).