From: Julia Lawall <julia.lawall@inria.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Data structures for source file analyses
Date: Sat, 26 Nov 2022 12:58:04 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2211261256520.15234@hadrien> (raw)
In-Reply-To: <433b8c36-21ac-2458-49bb-0bacea62b47b@web.de>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Sat, 26 Nov 2022, Markus Elfring wrote:
> >> How are preprocessor directives (for example) integrated into the taxonomy of
> >> the Coccinelle software?
> > I have no real idea what the above question means.
>
>
> I hope that further development ideas will influence software evolution
> in desirable directions.
>
>
>
> > Things that Coccinelle
> > is able to parse are put into the AST. Things that it is not able to
> > parse are attached as comments to neighboring tokens. There is no general
> > anser for preprocessing directives. Some are parsed and some are not.
>
> Would you become interested to export data from the mentioned “abstract syntax tree”
> and “control-flow graph” into any other standard file formats?
The control flow raph is already available in "dot" format, with the
option --control-flow-to-file
julia
prev parent reply other threads:[~2022-11-26 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 15:20 [cocci] Data structures for source file analyses Markus Elfring
2022-11-20 15:41 ` Julia Lawall
2022-11-20 16:00 ` Markus Elfring
[not found] ` <alpine.DEB.2.22.394.2211201702090.40755@hadrien>
2022-11-20 16:15 ` Markus Elfring
2022-11-26 10:20 ` Markus Elfring
2022-11-26 10:31 ` Julia Lawall
2022-11-26 10:48 ` Markus Elfring
2022-11-26 11:58 ` Julia Lawall [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=alpine.DEB.2.22.394.2211261256520.15234@hadrien \
--to=julia.lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.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 read-only IMAP folder(s) and NNTP newsgroup(s).