all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: esr@snark.thyrsus.com, emacs-devel@gnu.org
Subject: Re: Defending GCC considered futile
Date: Wed, 11 Feb 2015 18:13:17 -0500	[thread overview]
Message-ID: <E1YLgT7-0007nm-HW@fencepost.gnu.org> (raw)
In-Reply-To: <20150211104229.2782cb00@jabberwock.cb.piermont.com> (perry@piermont.com)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Yes, but that was long ago. More recently people have worked to make
  > GCC more modular

I don't know of any such work, but the GCC developers wouldn't normally
discuss it with me -- they would just do it.

		     and to re-use of GCC for other work, 

That's something else -- or, I should say, a broad range of many
different something elses.  Some of them are good and some are bad.

We want the modules of GCC to be combined with other modules _only by
linking_ so that the GPLm= must apply to the other modules.

On the other hand, connecting modules of GCC to other separate
programs is potentially dangerous.  For instance, outputting complete
ASTs from GCC is potentially dangerous.

People have presented arguments that it isn't really dangerous
nowadays.  They might be valid, and I want to consider them under calm
circumstances -- no pressure.

If I conclude it is ok for GCC to output the AST, are you interested
in working with that?

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! See stallman.org/skype.html.




  parent reply	other threads:[~2015-02-11 23:13 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 20:29 Defending GCC considered futile Eric S. Raymond
2015-02-07 21:24 ` David Kastrup
2015-02-09  0:04   ` Richard Stallman
2015-02-07 22:30 ` Florian Weimer
2015-02-08 14:12   ` Stefan Monnier
2015-02-09 19:39     ` Florian Weimer
2015-02-09 22:04   ` Perry E. Metzger
2015-02-09  0:04 ` Richard Stallman
2015-02-09  4:13   ` Stefan Monnier
2015-02-09  5:50   ` Stephen J. Turnbull
2015-02-09 22:06     ` Richard Stallman
2015-02-09 22:24       ` Perry E. Metzger
2015-02-10  3:37         ` Eli Zaretskii
2015-02-10  8:30           ` Daniel Colascione
2015-02-10  8:47             ` Helmut Eller
2015-02-10 15:58               ` Eli Zaretskii
2015-02-10 15:57             ` Eli Zaretskii
2015-02-10 18:19               ` Daniel Colascione
2015-02-10 18:41                 ` David Kastrup
2015-02-10 19:27                   ` Eli Zaretskii
2015-02-10 19:23                 ` Eli Zaretskii
2015-02-10 20:05                   ` David Kastrup
2015-02-10 23:14                   ` Stefan Monnier
2015-02-11  3:46                     ` Eli Zaretskii
2015-02-11 23:11                     ` Richard Stallman
2015-02-10 22:48         ` Richard Stallman
2015-02-11  2:08           ` John Yates
2015-02-11 15:42           ` Perry E. Metzger
2015-02-11 16:14             ` Eli Zaretskii
2015-02-11 16:29               ` Perry E. Metzger
2015-02-11 16:44                 ` Eli Zaretskii
2015-02-11 16:54                   ` Eli Zaretskii
2015-02-11 20:50                     ` Perry E. Metzger
2015-02-12  3:37                       ` Eli Zaretskii
2015-02-12  3:54                         ` Perry E. Metzger
2015-02-11 19:14                 ` Florian Weimer
2015-02-11 19:19                 ` Stefan Monnier
2015-02-11 23:13                 ` Richard Stallman
2015-02-12  1:48               ` raman
2015-02-11 23:13             ` Richard Stallman [this message]
2015-02-09  7:41   ` Helmut Eller
2015-02-09 19:30   ` Florian Weimer
2015-02-09 22:41     ` Perry E. Metzger
2015-02-10 22:46     ` Richard Stallman
2015-02-09 22:19   ` Perry E. Metzger

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=E1YLgT7-0007nm-HW@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@snark.thyrsus.com \
    --cc=perry@piermont.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.