From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Support for more programming languages?
Date: Mon, 18 Jul 2016 17:20:53 +0200 [thread overview]
Message-ID: <2c0fb3b6-966a-4d9a-9947-2d0701e4eb66@users.sourceforge.net> (raw)
In-Reply-To: <469DA7F6-6AC1-4040-AB2A-6A1DF1CDDF9D@mac.com>
> LLVM has been C++ from the beginning, and GCC is being rewritten in C++,
I guess that there are still various software development challenges evolving.
> though maybe with enough of a C flavor to be amenable to Coccinelle.
How do you think about common properties in the discussed programming
language mixture?
Do you find a feature request like "Exclusion of unsupported source code parts"
interesting for further consideration?
https://github.com/coccinelle/coccinelle/issues/20
Regards,
Markus
next prev parent reply other threads:[~2016-07-18 15:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 2:12 [Cocci] Coccinelle vs Firefox Perry Wagle
2016-07-17 5:47 ` Julia Lawall
2016-07-17 22:44 ` Perry Wagle
2016-07-18 2:05 ` Perry Wagle
2016-07-18 5:11 ` Julia Lawall
2016-07-18 11:34 ` Perry Wagle
2016-07-18 15:39 ` Julia Lawall
2016-07-18 23:17 ` Perry Wagle
2016-07-18 15:57 ` SF Markus Elfring
2016-07-18 23:26 ` Perry Wagle
2016-07-18 16:19 ` [Cocci] Object-orientation with SmPL? SF Markus Elfring
2016-07-18 23:31 ` Perry Wagle
2016-07-17 6:48 ` [Cocci] Support for more programming languages? SF Markus Elfring
2016-07-18 0:43 ` Perry Wagle
2016-07-18 15:20 ` SF Markus Elfring [this message]
2016-07-18 23:39 ` Perry Wagle
2016-07-19 7:57 ` SF Markus Elfring
2016-07-17 7:14 ` [Cocci] Transformations for Firefox source files SF Markus Elfring
2016-07-18 0:50 ` Perry Wagle
2016-07-18 15:27 ` SF Markus Elfring
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=2c0fb3b6-966a-4d9a-9947-2d0701e4eb66@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/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).