unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Pascal J. Bourguignon" <pjb@informatimago.com>
Cc: emacs-devel@gnu.org
Subject: Re: clang/emacs/ecb/semantic
Date: Sat, 01 Dec 2012 23:15:55 -0500	[thread overview]
Message-ID: <E1Tf0yB-0001k2-D0@fencepost.gnu.org> (raw)
In-Reply-To: <87zk1yhib2.fsf@kuiper.lan.informatimago.com> (pjb@informatimago.com)

    Wouldn't have been better to accept gcc-xml and have gcc cover 99% of
    the "market", rather than rejecting it, and eventually have gcc left
    with only 10% of the mind share, and clang/llvm 90%?  I'm afraid this
    might end like that.

We do not look at software users as a market.  Our goal is something
more than popularity.  What matters is users' freedom, and copyleft as
a weapon to defend it with.  GCC vs LLVM is important mainly as an instance
of fighting for copyleft.

    Would a good alternative (for freedom) to be that free compilers (GPL)
    provide the exact formal grammar they parse, so that tool builders could
    use it to write compatible parsers to use in their tools?

If "tool builders could use it to write compatible parsers to use in
their tools", is that good or is it bad?  You seem to think it is
always good.  I think it is good if the tools are free, and bad if the
tools are nonfree.  Nonfree tools (like any nonfree programs) are an
injustice.

Part of the reason why clang/llvm weakens our commnity, compared with
GCC, is that the clang front ends can feed their data to nonfree tools.

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call




  reply	other threads:[~2012-12-02  4:15 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 16:32 clang/emacs/ecb/semantic Ramneek Handa
2012-11-29 19:59 ` clang/emacs/ecb/semantic Dmitry Gutov
2012-11-29 20:27   ` clang/emacs/ecb/semantic David Engster
2012-11-29 20:38     ` clang/emacs/ecb/semantic Óscar Fuentes
2012-11-29 20:49       ` clang/emacs/ecb/semantic David Engster
2012-11-30  2:52       ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30  6:34         ` clang/emacs/ecb/semantic Pascal J. Bourguignon
2012-11-30 15:15           ` clang/emacs/ecb/semantic David Engster
2012-11-30 15:25             ` clang/emacs/ecb/semantic ramneek
2012-12-01  4:44               ` clang/emacs/ecb/semantic Richard Stallman
2012-12-04 17:04                 ` clang/emacs/ecb/semantic David Engster
2012-11-30 20:11           ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30 21:02             ` clang/emacs/ecb/semantic Óscar Fuentes
2012-12-01 19:30               ` clang/emacs/ecb/semantic Richard Stallman
2012-12-01 19:30               ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30 21:50             ` clang/emacs/ecb/semantic Pascal J. Bourguignon
2012-12-02  4:15               ` Richard Stallman [this message]
2012-12-02  5:13                 ` clang/emacs/ecb/semantic Daniel Colascione
2012-12-03  0:02                   ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03  1:42                     ` clang/emacs/ecb/semantic Daniel Colascione
2012-12-03 17:08                       ` clang/emacs/ecb/semantic Eli Zaretskii
2012-12-03 17:21                         ` clang/emacs/ecb/semantic Chong Yidong
2012-12-03 17:56                           ` clang/emacs/ecb/semantic Eli Zaretskii
2012-12-03 18:14                             ` clang/emacs/ecb/semantic Daniel Colascione
2012-12-03 18:50                               ` clang/emacs/ecb/semantic Eli Zaretskii
2012-12-03 19:37                                 ` clang/emacs/ecb/semantic Stefan Monnier
2012-12-04  0:51                                   ` clang/emacs/ecb/semantic joakim
2012-12-04  2:17                                     ` clang/emacs/ecb/semantic Stefan Monnier
2012-12-04  1:04                                   ` clang/emacs/ecb/semantic joakim
2012-12-04  0:41                               ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03 19:34                       ` clang/emacs/ecb/semantic Richard Stallman
2012-12-02  9:04                 ` clang/emacs/ecb/semantic Stephen J. Turnbull
2012-12-02 13:48                   ` clang/emacs/ecb/semantic Helmut Eller
2012-12-03  0:02                     ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03 16:02                       ` clang/emacs/ecb/semantic Burton Samograd
2012-12-04  0:40                         ` clang/emacs/ecb/semantic Richard Stallman
2012-12-04 14:05                           ` clang/emacs/ecb/semantic Miguel Guedes
2012-12-05 11:49                             ` clang/emacs/ecb/semantic Richard Stallman
2012-12-05 17:21                             ` clang/emacs/ecb/semantic Paul Eggert
2012-12-03  0:02                   ` clang/emacs/ecb/semantic Richard Stallman
2012-12-02 13:59                 ` clang/emacs/ecb/semantic Pascal J. Bourguignon
2012-12-03  0:02                   ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03  0:02                   ` clang/emacs/ecb/semantic Richard Stallman
2012-12-03  0:02                   ` clang/emacs/ecb/semantic Richard Stallman
2012-11-30  6:46         ` clang/emacs/ecb/semantic Helmut Eller
2012-11-30  2:51 ` clang/emacs/ecb/semantic Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Tf0yB-0001k2-D0@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pjb@informatimago.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 public inbox

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

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