From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, Coccinelle <cocci@systeme.lip6.fr>
Cc: Denis Efremov <efremov@linux.com>, Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] coccinelle: api: add kzfree script
Date: Fri, 5 Jun 2020 07:50:18 +0200 [thread overview]
Message-ID: <27351b7d-cead-1c83-4ff1-5a94df9adec5@web.de> (raw)
> On the other hand, do you really require E to be a pointer?
> If you do that, it will have to find the type of E.
I suggest to reconsider this information.
> If E refers to a structure field, then the type might not be available
> in the current function, and you may need command line argments like
> --all-includes or --recursive-includes.
Will the software documentation need corresponding extensions for
the safe application of the semantic patch language?
Will the used data structure access operator like arrow or dot
influence the interpretation of the software situation?
> Is avoiding transforming the case where E is not verified
> to be a pointer a concern?
I would find it desirable to express constraints for pointer data types
according to the applied programming interfaces.
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, Coccinelle <cocci@systeme.lip6.fr>
Cc: Joe Perches <joe@perches.com>, linux-kernel@vger.kernel.org
Subject: Re: [Cocci] [PATCH v2] coccinelle: api: add kzfree script
Date: Fri, 5 Jun 2020 07:50:18 +0200 [thread overview]
Message-ID: <27351b7d-cead-1c83-4ff1-5a94df9adec5@web.de> (raw)
> On the other hand, do you really require E to be a pointer?
> If you do that, it will have to find the type of E.
I suggest to reconsider this information.
> If E refers to a structure field, then the type might not be available
> in the current function, and you may need command line argments like
> --all-includes or --recursive-includes.
Will the software documentation need corresponding extensions for
the safe application of the semantic patch language?
Will the used data structure access operator like arrow or dot
influence the interpretation of the software situation?
> Is avoiding transforming the case where E is not verified
> to be a pointer a concern?
I would find it desirable to express constraints for pointer data types
according to the applied programming interfaces.
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next reply other threads:[~2020-06-05 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 5:50 Markus Elfring [this message]
2020-06-05 5:50 ` [Cocci] [PATCH v2] coccinelle: api: add kzfree script Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2020-06-05 6:43 Markus Elfring
2020-06-05 6:43 ` Markus Elfring
2020-06-04 14:08 [PATCH] " Denis Efremov
2020-06-04 20:48 ` [PATCH v2] " Denis Efremov
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=27351b7d-cead-1c83-4ff1-5a94df9adec5@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=efremov@linux.com \
--cc=joe@perches.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
/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.