public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Searching function implementations with more than a single return?
Date: Tue, 1 Jul 2025 16:06:21 +0200	[thread overview]
Message-ID: <20d8778f-27fa-43ff-97e1-44375755d952@web.de> (raw)
In-Reply-To: <d0fb31c8-2888-47e6-c527-57f0e828f32d@inria.fr>

>> Would you like to suggest the exclusion of a single return statement
>> by a more appropriate source code search approach?
> Requiring the presence of a declaration already excludes the case of a
> single return.

Variable declarations (and definition) can also be specified after
a return statement, can't they?


>                 If you want to exclude a single return after a
> declaration, then the return should be put in the disjunctions with the
> *s.  The *sl will again never match anything, because it's not coming
> immediately after a {}.  It comes immediately after a declaration.

Is the handling of curly brackets (for compound statements) still unclear
so far?

Regards,
Markus


  reply	other threads:[~2025-07-01 14:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01  8:01 [cocci] Searching function implementations with more than a single return? Markus Elfring
2025-07-01 11:54 ` [cocci] Searching function implementations with variable declarations and statements? Markus Elfring
2025-07-01 12:09   ` Julia Lawall
2025-07-01 12:26     ` Markus Elfring
2025-07-01 12:29       ` Julia Lawall
2025-07-01 12:00 ` Markus Elfring
2025-07-01 12:42   ` Markus Elfring
2025-07-01 13:41     ` Julia Lawall
2025-07-01 13:55       ` Markus Elfring
2025-07-01 14:01         ` Julia Lawall
2025-07-01 13:01 ` [cocci] Searching function implementations with more than a single return? Markus Elfring
2025-07-01 13:40   ` Julia Lawall
2025-07-01 13:50     ` Markus Elfring
2025-07-01 13:59       ` Julia Lawall
2025-07-01 14:06         ` Markus Elfring [this message]
2025-07-01 15:17           ` Julia Lawall
2025-07-01 18:00             ` Markus Elfring
2025-07-02  9:11             ` [cocci] Search challenges for “statement lists”? Markus Elfring
2025-07-03 10:00             ` [cocci] Using statement list combinations? Markus Elfring
2025-07-03 10:23               ` Julia Lawall
2025-07-03 10:28                 ` Markus Elfring
2025-07-03 11:54                   ` Julia Lawall
2025-07-03 13:25                     ` 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=20d8778f-27fa-43ff-97e1-44375755d952@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=julia.lawall@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