From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Increasing awareness for short-circuit evaluation consequences by SmPL disjunctions?
Date: Wed, 5 Feb 2025 13:20:25 +0100 [thread overview]
Message-ID: <6d571cb5-ed04-426f-8375-0c3c2ba3ef6d@web.de> (raw)
In-Reply-To: <9cfd83f7-cc7-fbf-1432-c3ce47337987@inria.fr>
>> The usage incidence might be unclear for involved case distinctions.
>> How do you think about to clarify possibilities any further for the reordering of
>> SmPL disjunction items?
>
> What is unclear?
* How will chances evolve to improve the software documentation for
mentioned functionality?
* How often can case distinctions actually be applied in an analysed
source file?
> The disjunction branches are not reordered.
Are there system configuration and software development concerns to consider
just because of short-circuit evaluation?
Regards,
Markus
prev parent reply other threads:[~2025-02-05 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 12:05 [cocci] Increasing awareness for short-circuit evaluation consequences by SmPL disjunctions? Markus Elfring
2025-02-05 12:11 ` Julia Lawall
2025-02-05 12:20 ` Markus Elfring [this message]
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=6d571cb5-ed04-426f-8375-0c3c2ba3ef6d@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).