From: wagle@mac.com (Perry Wagle)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Transformations for Firefox source files
Date: Sun, 17 Jul 2016 17:50:58 -0700 [thread overview]
Message-ID: <80E0E659-6BED-4A87-AEF6-DE5775583B12@mac.com> (raw)
In-Reply-To: <d03d92ec-2cbd-8c31-3cdc-c1982425b684@users.sourceforge.net>
> On Jul 17, 2016, at 12:14 AM, SF Markus Elfring <elfring@users.sourceforge.net> wrote:
>
>> So my question is whether you guys think Coccinelle would be useful to me
>> in comprehending and doing MASS transformations of the firefox source?
>
> For which kind of source code transformations are you especially interested in?
With Firefox, it the excision of the bookmarks subsystem from a current (moving target) source tree and replacing it with my own. I might want to turn it into an extension first, and to turn my extension into a subsystem.
> With which search patterns would you like to achieve further software improvements?
I don?t know yet. Depends on what I can do. II?m just skimmed some of the documentation, checking to see if I should dive in.
> Regards,
> Markus
next prev parent reply other threads:[~2016-07-18 0:50 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
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 [this message]
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=80E0E659-6BED-4A87-AEF6-DE5775583B12@mac.com \
--to=wagle@mac.com \
--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).