linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Bouchard <matju@artengine.ca>
To: linux-sparse@vger.kernel.org
Subject: support for C++ ?
Date: Mon, 25 Jun 2007 22:20:51 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706252219310.12395@paik.artengine.ca> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 339 bytes --]


Are there any plans for supporting C++ or any subset thereof? (e.g. 
parsing G++4 syntax but perhaps skipping over some constructs that are 
difficult to handle if it's too much work for now)

thanks.

  _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada

             reply	other threads:[~2007-06-26  2:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26  2:20 Mathieu Bouchard [this message]
2007-06-26  5:11 ` support for C++ ? Josh Triplett
2007-06-26 11:01   ` Jeff Garzik
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=Pine.LNX.4.64.0706252219310.12395@paik.artengine.ca \
    --to=matju@artengine.ca \
    --cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).