From: Michael Stefaniuc <mstefani@mykolab.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Missing support in SmPL for wide char character constants and string literals
Date: Fri, 4 Oct 2019 21:37:37 +0200 [thread overview]
Message-ID: <05519e65-6b3e-989b-066e-8239a4539151@mykolab.com> (raw)
In-Reply-To: <c9a64f4a-30fd-7c99-bd29-edbda0b30337@web.de>
On 10/3/19 10:17 AM, Markus Elfring wrote:
>> A test case is attached as a patch for the coccinelle tests.
>
> * Can the specification “#include <wchar.h>” become relevant for
> your source code example?
Did you try it out yourself?
> https://en.cppreference.com/w/c/string/multibyte#Types
Yes, that says that the char16_t and char32_t are defined in uchar.h.
bye
michael
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-10-04 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 21:05 [Cocci] Missing support in SmPL for wide char character constants and string literals Michael Stefaniuc
2019-10-03 5:45 ` Julia Lawall
2019-10-03 9:16 ` Markus Elfring
2019-10-03 20:09 ` Michael Stefaniuc
2019-10-03 8:17 ` Markus Elfring
2019-10-04 19:37 ` Michael Stefaniuc [this message]
2019-10-03 10:48 ` Markus Elfring
2019-10-04 22:07 ` Julia Lawall
2019-10-05 20:33 ` Michael Stefaniuc
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=05519e65-6b3e-989b-066e-8239a4539151@mykolab.com \
--to=mstefani@mykolab.com \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.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).