From: Ken Raeburn <raeburn@raeburn.org>
To: rms@gnu.org
Cc: alinsoar@voila.fr, Emacs-devel@gnu.org
Subject: Re: Splint
Date: Fri, 8 Jan 2010 12:35:06 -0500 [thread overview]
Message-ID: <28535EDD-D486-419B-83B0-D7E9962DD36D@raeburn.org> (raw)
In-Reply-To: <E1NTEiB-00080n-MZ@fencepost.gnu.org>
On Jan 8, 2010, at 08:17, Richard Stallman wrote:
> While Coverity's stuff is commercial,
>
> Do you mean "proprietary"? They are not the same. There is nothing
> wrong with a program's being commercial. See
> http://www.gnu.org/philosophy/words-to-avoid.html.
Yes, sorry, I mis-spoke.
> they've offered its use to some
> open-source/free software projects.
>
> See http://www.gnu.org//philosophy/mcvoy.html
> for the story about another similar offer,
> and the harm that was done when someone else accepted it.
Yep, there is that issue. At least in this case it is still practical
and easy for someone to use splint and other free or at least open-
source software, while someone else uses something like Coverity's
tools. Unlike Bitkeeper and Linux kernel source access, the
proprietary tools shouldn't intrude significantly on those who don't
want to use it in their development work.
I'd still love to see a free tool to do this work. But when I did a
survey for work a few years back, my impression was that the free
tools were all poor; splint appeared to be one of the best of the lot,
and was quite a pain to try to use. Perhaps with recent work on gcc,
llvm and other tools, the situation can be changed.
Ken
prev parent reply other threads:[~2010-01-08 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 10:43 Splint alin.s
2010-01-07 13:50 ` Splint Ken Raeburn
2010-01-07 15:03 ` Splint Dan Nicolaescu
2010-01-08 13:17 ` Splint Richard Stallman
2010-01-08 17:35 ` Ken Raeburn [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
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=28535EDD-D486-419B-83B0-D7E9962DD36D@raeburn.org \
--to=raeburn@raeburn.org \
--cc=Emacs-devel@gnu.org \
--cc=alinsoar@voila.fr \
--cc=rms@gnu.org \
/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).