All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Restore source code from matched expressions?
Date: Wed, 02 Apr 2014 12:55:22 +0200	[thread overview]
Message-ID: <533BEC9A.60208@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1404021033420.2080@hadrien>

>> Are there any chances that this software will become able to restore a preferred
>> source code layout from the matched expressions?
> 
> No, a metavariable contains no information about its format, so that it
> can match with other metavariables, and when it is printed, Coccinelle
> follows whatever strategy it follows, which is intended to follow the
> conventions of Linux, but is not always successful.

Do SmPL metavariables also manage the start and end positions for the source
code part which was matched in a specific analysis context?
Is such information not only available for position metavariables?

Regards,
Markus

  parent reply	other threads:[~2014-04-02 10:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 17:42 [Cocci] coccinelle: trivial linux code style reformatting Joe Perches
2014-04-01 18:29 ` Peter Senna Tschudin
2014-04-01 23:11   ` Joe Perches
2014-04-02  5:53     ` Julia Lawall
2014-04-02  5:57       ` Joe Perches
2014-04-02  8:30       ` [Cocci] "trivial" " SF Markus Elfring
2014-04-02  8:35         ` Julia Lawall
2014-04-02  9:00           ` [Cocci] " SF Markus Elfring
2014-04-02 10:55           ` SF Markus Elfring [this message]
2014-04-01 20:02 ` [Cocci] "trivial" linux " SF Markus Elfring
2014-04-01 23:26   ` Joe Perches
2014-04-02  7:19 ` [Cocci] Clarification for source " SF Markus Elfring
2014-04-02  7:43   ` Julia Lawall
2014-04-02  7:53     ` SF Markus Elfring
2014-04-02  8:33       ` Julia Lawall
2014-04-02  7:56   ` Joe Perches

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=533BEC9A.60208@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.