Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Data processing for expression ASTs
Date: Mon, 13 Jul 2015 15:00:12 +0200	[thread overview]
Message-ID: <55A3B65C.9080708@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1507130743580.2561@hadrien>

>> How are the chances that more documentation will become available
>> for safe processing of corresponding abstract syntax graph instances?
> 
> About the same as the chance that a user who wants the documentation will
> write it.  I have no plans to do so.  In general, if you know enough OCaml
> to use the abstract syntax tree, you also know enough OCaml to figure out
> what it is from the source code.  Everything is defined in
> parsing_c/ast_c.ml.

Does this "tree" data structure correspond to the complete input from
the source file?

I imagine that a special mapping for expression data should be sufficient
for the discussed SmPL metavariable, shouldn' it?

Regards,
Markus

  parent reply	other threads:[~2015-07-13 13:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  7:19 [Cocci] Error predicate determination with SmPL? SF Markus Elfring
2015-07-13 10:55 ` SF Markus Elfring
2015-07-13 11:00   ` Julia Lawall
2015-07-13 11:14     ` SF Markus Elfring
2015-07-13 11:46       ` Julia Lawall
2015-07-13 12:01         ` SF Markus Elfring
2015-07-13 13:00         ` SF Markus Elfring [this message]
2015-07-13 16:19     ` SF Markus Elfring
2015-07-13 17:02       ` Julia Lawall
2015-07-13 17:10         ` SF Markus Elfring
2015-07-13 17:20         ` SF Markus Elfring
2015-07-13 17:24           ` Julia Lawall
2015-07-13 17:39             ` [Cocci] Checking of OCaml functionality SF Markus Elfring
2015-07-13 17:48               ` Julia Lawall
2015-07-13 18:03                 ` SF Markus Elfring
2015-07-13 18:07                   ` Julia Lawall
2015-07-13 18:11                     ` SF Markus Elfring
2015-07-13 18:15                       ` Julia Lawall

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=55A3B65C.9080708@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