All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek M Jones <derek@knosof.co.uk>
To: Josh Triplett <josh@freedesktop.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	Mathieu Bouchard <matju@artengine.ca>,
	linux-sparse@vger.kernel.org
Subject: Re: support for C++ ?
Date: Tue, 26 Jun 2007 14:21:49 +0100	[thread overview]
Message-ID: <468112ED.7050104@knosof.co.uk> (raw)
In-Reply-To: <46811043.90207@freedesktop.org>

Josh,

> While a C++ parser would add significant complexity to Sparse, I would still
> prefer to integrate it rather than encouraging people to fork.  I think a
> reasonable amount of code sharing would still exist between the C and C++
> code, and ideally almost all of the backend code would support both.

Experience suggests that a C++ front end is around a factor of seven
times larger than a C front end.

There are many more syntactic ambiguities in C++ that require
symbol table information to resolve (even then life can be tough).

Code sharing would be possible in the sense that if a C++ parser
were implemented it would be close to handling C out of the box.

-- 
Derek M. Jones                              tel: +44 (0) 1252 520 667
Knowledge Software Ltd                      mailto:derek@knosof.co.uk
Applications Standards Conformance Testing    http://www.knosof.co.uk

      reply	other threads:[~2007-06-26 13:21 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
2007-06-26 13:10     ` Josh Triplett
2007-06-26 13:21       ` Derek M Jones [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=468112ED.7050104@knosof.co.uk \
    --to=derek@knosof.co.uk \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.