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] Checking signal handler implementations with SmPL
Date: Wed, 15 Jul 2015 22:38:25 +0200	[thread overview]
Message-ID: <55A6C4C1.9060600@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1507151023270.2919@hadrien>

> Furthermore, ... matches the shortest path between two points.

It seems that I am still not so used to all combinations of the SmPL ellipsis.


> That is, in your rule, you will only match the case where a control-flow patch
> contains exactly one call to either exit or fprintf.  If you want to allow
> more occurrences, you can use <... ...> with searches for 0 or more or
> something, or <+... ...+> which searches for one or more.

I guess that the last option is more appropriate for my source code
search pattern.

Thanks for your explanation.

Regards,
Markus

  reply	other threads:[~2015-07-15 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  7:09 [Cocci] Checking signal handler implementations with SmPL SF Markus Elfring
2015-07-15 14:27 ` Julia Lawall
2015-07-15 20:38   ` SF Markus Elfring [this message]
2015-07-16  5:41 ` [Cocci] Deletion of blank lines? SF Markus Elfring
2015-07-17  9:50   ` Julia Lawall
2015-07-17 11:12     ` 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=55A6C4C1.9060600@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.