From: Tommy Vercetti <vercetti@zlew.org>
To: gcc@gcc.gnu.org
Subject: Re: c/c++ validator
Date: Sun, 19 Jun 2005 01:44:00 -0000 [thread overview]
Message-ID: <200506190344.07131@gj-laptop> (raw)
In-Reply-To: <m3y897i2ep.fsf@uniton.integrable-solutions.net>
On Sunday 19 June 2005 03:03, you wrote:
> Tommy Vercetti <vercetti@zlew.org> writes:
> | On Sunday 19 June 2005 00:32, you wrote:
> | > Something like:
> | >
> | > http://www.cs.rpi.edu/~gregod/STLlint/STLlint.html
> |
> | Yeah, but for more than just STL, and opensource. C++ checker that
> | is going to work for instance for KDE.
> | Wonder why they use proprietary parser,
>
> maybe because they work? ;-p
> | there are opensource
> | parsers around, like elsa, or gcc c++ parser.
>
> Elsa does not parse C++.
Elsa is for C/C++, so it says on their website.
> GCC/g++ parser is tightly integrated to GCC.
>
> Most of the tools I know of are either "research projects" (which
> means that they basically "die" when the professor get promoted or the
> students graduate; they are lots of them out there) or are/ use
> proprietary tools.
>
> We need to get GCC/g++ to a competing level of usefulness but the road
> is not quite that straight.
Yep.
Btw, don't have to cc me, I'm reading that list.
--
Vercetti
next prev parent reply other threads:[~2005-06-19 1:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 22:24 Tommy Vercetti
2005-06-18 22:32 ` Mathieu Malaterre
2005-06-18 22:38 ` Tommy Vercetti
2005-06-19 1:03 ` Gabriel Dos Reis
2005-06-19 1:44 ` Tommy Vercetti [this message]
2005-06-19 2:05 ` Gabriel Dos Reis
2005-06-19 2:16 ` Mathieu Malaterre
2005-06-19 2:48 ` Gabriel Dos Reis
2005-06-19 20:58 ` Tommy Vercetti
2005-06-20 19:53 ` Kai Henningsen
2005-06-20 20:58 ` Tommy Vercetti
2005-06-19 3:04 ` Mark Loeser
2005-06-19 2:41 Florian Krohm
2005-06-19 23:59 David Bremner
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=200506190344.07131@gj-laptop \
--to=vercetti@zlew.org \
--cc=gcc@gcc.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.
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).