From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, Denis Efremov <efremov@linux.com>
Cc: cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: Re: [v3] coccinelle: misc: add array_size_dup script to detect missed overflow checks
Date: Mon, 22 Jun 2020 13:54:40 +0200 [thread overview]
Message-ID: <d23eec1d-9e5d-87bd-be8a-9e5b1c00a922@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2006221321180.2531@hadrien>
>> I suggest to take another look at information from the section
>> “2.4.3. Formatted string literals”.
>> https://docs.python.org/3/reference/lexical_analysis.html#f-strings
>>
>> This software documentation provides the information “New in version 3.6”.
>> Will such a detail trigger any more software development consequences?
>
> Thanks foor this information. Denis, would it be possible to express the
> code in a more portable way?
Which is the last revision of the Python programming language
that you would like to support so far?
Regards,
Markus
prev parent reply other threads:[~2020-06-22 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 11:17 [v3] coccinelle: misc: add array_size_dup script to detect missed overflow checks Markus Elfring
2020-06-22 11:22 ` Julia Lawall
2020-06-22 11:54 ` 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=d23eec1d-9e5d-87bd-be8a-9e5b1c00a922@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=efremov@linux.com \
--cc=julia.lawall@inria.fr \
--cc=keescook@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox