From: Jeff Garzik <jeff@garzik.org>
To: Josh Triplett <josh@freedesktop.org>
Cc: Mathieu Bouchard <matju@artengine.ca>, linux-sparse@vger.kernel.org
Subject: Re: support for C++ ?
Date: Tue, 26 Jun 2007 07:01:29 -0400 [thread overview]
Message-ID: <4680F209.7070601@garzik.org> (raw)
In-Reply-To: <4680A013.8030707@freedesktop.org>
Josh Triplett wrote:
> To the best of my knowledge, nobody involved in the Sparse community has any
> plans to attempt C++. I also think that a subset of the language capable of
> handling any significant number of common programs would end up containing
> most of the language. Even basic support for C++ would require large changes
> to the parser and to the Sparse data structures, and that doesn't even count
> the huge can of worms that would open once you start running into interactions
> between Sparse-annotated types and inheritance or overloading.
Indeed. The gcc people even wrote their own hand-coded C++ parser for
similar reasons, so I can't see it being an easy integration into
sparse. You might as well fork at that point.
Jeff
next prev parent reply other threads:[~2007-06-26 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 2:20 support for C++ ? Mathieu Bouchard
2007-06-26 5:11 ` Josh Triplett
2007-06-26 11:01 ` Jeff Garzik [this message]
2007-06-26 13:10 ` Josh Triplett
2007-06-26 13:21 ` Derek M Jones
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=4680F209.7070601@garzik.org \
--to=jeff@garzik.org \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=matju@artengine.ca \
/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 NNTP newsgroup(s).