From: wagle@mac.com (Perry Wagle)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Object-orientation with SmPL?
Date: Mon, 18 Jul 2016 16:31:47 -0700 [thread overview]
Message-ID: <5F7F044E-7B47-4780-9EBF-DCD48BB67EBD@mac.com> (raw)
In-Reply-To: <e59a3304-dd48-ba37-cd9e-eb5dc4694a70@users.sourceforge.net>
> On Jul 18, 2016, at 9:19 AM, SF Markus Elfring <elfring@users.sourceforge.net> wrote:
>
>> I was also wondering if object orientation threw Coccinelle off.
>
> This software provides also a few classes for the programming languages
> "OCaml" and "Python". Are you thinking about further extensions?
>
> Would you like to give the topic "Class libraries for software components"
> another look?
> https://github.com/coccinelle/coccinelle/issues/22
>
>
>> Probably not if you found a way to chase function pointers statically.
>
> How will pointers matter for your source code search pattern?
In comprehending Linux Kernel source in the past, I?ve been stymied by not knowing where all a function pointer in a struct of function pointers might go during manual call graphing. Automating this would be nice.
next prev parent reply other threads:[~2016-07-18 23:31 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 [this message]
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
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=5F7F044E-7B47-4780-9EBF-DCD48BB67EBD@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).