From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Parsing C source files by Coccinelle
Date: Tue, 8 Mar 2016 10:01:49 +0100 [thread overview]
Message-ID: <56DE94FD.3030707@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1603080728340.2647@hadrien>
>> An option like "--enable-menhirLib" is provided under the configuration category
>> "Optional Features", isn't it?
>
> This is for the parsing of the semantic patch.
Does this information mean that the software library "Menhir" is not so optional at the moment?
> Not the parsing of the C code.
Is the tool "ocamlyacc" sufficient for this data processing so far?
>>> Yoann Padioleau:
>>> Parsing C/C++ Code without Pre-processing. CC 2009: 109-125
>>
>> How much did the software design and corresponding implementation evolve further
>> since the description of this approach?
>
> Not at all.
I have got an other impression through the years.
Your software supports source code transformations also without including header files
and other pre-processing stuff.
Example:
The option "--include-headers-for-types" was added by the release "Coccinelle 1.0.0-rc22".
A developer should decide whether header information is needed for a script in the semantic
patch language or not.
Would you like to increase the usage of "Menhir" as a LR(1) parser generator for the OCaml
programming language.
Regards,
Markus
next prev parent reply other threads:[~2016-03-08 9:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 0:43 [Cocci] Coccinelle Compilation Problem: configure file Aftab Hussain
2016-03-04 7:09 ` Julia Lawall
2016-03-07 15:54 ` Aftab Hussain
2016-03-08 8:57 ` Sébastien Hinderer
2016-03-04 14:32 ` [Cocci] Regeneration of the script "configure" for Coccinelle SF Markus Elfring
[not found] ` <CAO=9Y+2Qm+A9a91zGrYNJavOXcWFR2hj5Xx+=FPG1p02KdC7Ew@mail.gmail.com>
2016-03-07 18:39 ` [Cocci] Parsing C source files by Coccinelle SF Markus Elfring
[not found] ` <CAO=9Y+0KUsrK4OpR9YrNpp5JJ2tDDoY-DOq0xfDBcY8GdKWwCQ@mail.gmail.com>
2016-03-07 19:55 ` SF Markus Elfring
2016-03-08 9:59 ` Iago Abal
2016-03-08 10:26 ` SF Markus Elfring
2016-03-08 12:01 ` Iago Abal
2016-03-08 13:50 ` SF Markus Elfring
2016-03-09 13:42 ` Iago Abal
2016-03-09 16:34 ` SF Markus Elfring
2016-03-10 1:02 ` Julia Lawall
2016-03-07 21:57 ` Julia Lawall
2016-03-07 22:20 ` SF Markus Elfring
2016-03-07 22:29 ` Julia Lawall
2016-03-08 9:01 ` SF Markus Elfring [this message]
2016-03-08 10:55 ` Julia Lawall
2016-03-08 11:43 ` [Cocci] Checking build parameters for Menhir SF Markus Elfring
2016-03-08 9:00 ` [Cocci] Parsing C source files by Coccinelle Sébastien Hinderer
2016-03-08 9:20 ` SF Markus Elfring
2016-03-08 9:25 ` Sébastien Hinderer
2016-03-08 9:33 ` 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=56DE94FD.3030707@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