cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Support for more programming languages?
Date: Sun, 17 Jul 2016 08:48:51 +0200	[thread overview]
Message-ID: <76bf1017-d629-d44a-5493-0dcccbbfa65b@users.sourceforge.net> (raw)
In-Reply-To: <009C7972-C7EB-4B7F-ABC5-A1C0C1CA5797@mac.com>

> The main problem is that firefox is written in a variety of programming languages.

https://www.quora.com/What-programming-languages-are-web-browsers-like-Google-Chrome-Opera-and-Mozilla-Firefox-written-in


> How hard would it be to retarget Coccinelle to those languages?

The Coccinelle software is concentrating on source code transformations
for the programming language "C" so far.
For which languages do you look for improvements finally?

* How would you like to improve tools for context-dependant languages like "C++"?

* How ambitious are you to support further software development around such areas?

Regards,
Markus

  parent reply	other threads:[~2016-07-17  6:48 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 ` SF Markus Elfring [this message]
2016-07-18  0:43   ` [Cocci] Support for more programming languages? Perry Wagle
2016-07-18 15:20     ` SF Markus Elfring
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=76bf1017-d629-d44a-5493-0dcccbbfa65b@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).