From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Clarification for application of null pointer checks with SmPL
Date: Wed, 11 Mar 2020 09:15:21 +0100 [thread overview]
Message-ID: <c4abeef9-3237-ee89-9149-2a7e1341f95f@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2003110909390.2439@hadrien>
>>> pointer == NULL would have been sufficient (not related to the noted problems).
>>
>> Should this detail be handled as an isomorphism?
>> https://github.com/coccinelle/coccinelle/blob/19ee1697bf152d37a78a20cefe148775bf4b0e0d/standard.iso#L134
>
> Yes.
Unfortunately, I might stumble still on difficulties for the understanding of desired
and actually observed software behaviour (because of remaining open issues).
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
prev parent reply other threads:[~2020-03-11 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 13:26 [Cocci] Checking two error messages Markus Elfring
2020-03-08 14:42 ` Julia Lawall
2020-03-11 7:56 ` [Cocci] Clarification for application of null pointer checks with SmPL Markus Elfring
2020-03-11 8:10 ` Julia Lawall
2020-03-11 8:15 ` 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=c4abeef9-3237-ee89-9149-2a7e1341f95f@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.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 NNTP newsgroup(s).