From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Coccinelle for other programming languages
Date: Fri, 18 Dec 2015 09:00:36 +0100 [thread overview]
Message-ID: <5673BD24.5000900@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1512171825240.10291@hadrien>
>> I?m curious whether you can comment on any other tools for other programming languages.
How do you think about to take another look at issues like the following?
> Coccinelle doesn't support any languages other than C, and a small amount of C++.
Support C++ codebases
https://github.com/coccinelle/coccinelle/issues/1
How many design elements can be shared for programming languages
which have got similar properties?
https://en.wikipedia.org/wiki/Procedural_programming
> For C++, it parses the C-like parts of the code, and ignores the rest.
Exclusion of unsupported source code parts
https://github.com/coccinelle/coccinelle/issues/20
> It could be conceptually possible to design a version of Coccinelle
> for other languages, but it would require a lot of development work,
> so funding would be required.
Class libraries for software components
https://github.com/coccinelle/coccinelle/issues/22
Regards,
Markus
prev parent reply other threads:[~2015-12-18 8:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 16:38 [Cocci] Coccinelle for other programming languages Dharmalingam Ganesan
2015-12-17 17:28 ` Julia Lawall
2015-12-17 22:11 ` Luis R. Rodriguez
2015-12-18 8:09 ` SF Markus Elfring
2015-12-18 14:52 ` Dharmalingam Ganesan
2015-12-18 15:11 ` Julia Lawall
2015-12-18 16:28 ` Dharmalingam Ganesan
2015-12-18 16:46 ` Julia Lawall
2015-12-18 17:53 ` Dharmalingam Ganesan
2015-12-18 18:11 ` Julia Lawall
2015-12-19 8:12 ` SF Markus Elfring
2015-12-18 8:00 ` SF Markus Elfring [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=5673BD24.5000900@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