From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3821 invoked by alias); 19 Jun 2005 01:03:13 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 3798 invoked by uid 22791); 19 Jun 2005 01:03:08 -0000 Received: from smtp-100-sunday.nerim.net (HELO kraid.nerim.net) (62.4.16.100) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 19 Jun 2005 01:03:08 +0000 Received: from uniton.integrable-solutions.net (gdr.net1.nerim.net [62.212.99.186]) by kraid.nerim.net (Postfix) with ESMTP id EE7C040E1E; Sun, 19 Jun 2005 03:03:04 +0200 (CEST) Received: from uniton.integrable-solutions.net (localhost [127.0.0.1]) by uniton.integrable-solutions.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j5J13AKY024334; Sun, 19 Jun 2005 03:03:10 +0200 Received: (from gdr@localhost) by uniton.integrable-solutions.net (8.12.10/8.12.10/Submit) id j5J13Atu024333; Sun, 19 Jun 2005 03:03:10 +0200 To: Tommy Vercetti Cc: gcc@gcc.gnu.org Subject: Re: c/c++ validator References: <200506190024.18033@gj-laptop> <42B4A0F6.4010303@nycap.rr.com> <200506190038.07506@gj-laptop> From: Gabriel Dos Reis In-Reply-To: <200506190038.07506@gj-laptop> Date: Sun, 19 Jun 2005 01:03:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-06/txt/msg00783.txt.bz2 Tommy Vercetti 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++. 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. -- Gaby