From: Michael Stefaniuc <mstefani@mykolab.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Missing support in SmPL for wide char character constants and string literals
Date: Thu, 3 Oct 2019 22:09:24 +0200 [thread overview]
Message-ID: <24b4e9ee-f2c6-e46c-ef27-f911bdca53f8@mykolab.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1910030745320.2638@hadrien>
On 10/3/19 7:45 AM, Julia Lawall wrote:
>
>
> On Wed, 2 Oct 2019, Michael Stefaniuc wrote:
>
>> Hello!
>>
>> SmPL doesn't support the character constants of the form:
>> u'c', U'c', L'c'
>>
>> nor the string literals of the form:
>> u8"", u"", U"", L""
>
> What is the type of these things?
The test patch has the types in it, but here they are again:
u8"" ==> char[]
u"" ==> char16_t[]
U"" ==> char32_t[]
L"" ==> wchar_t[] (which depends on the compilation flags, 32bit
normally but 16bit with mingw and Wine)
bye
michael
>>
>> A test case is attached as a patch for the coccinelle tests.
>>
>> minus: parse error:
>> File "tests/wchar.cocci", line 8, column 22, charpos = 106
>> around = ''',
>> whole content = - char16_t zero = u'\0';
>>
>>
>> thanks
>> bye
>> michael
>>
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-10-03 20:09 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 [this message]
2019-10-03 8:17 ` Markus Elfring
2019-10-04 19:37 ` Michael Stefaniuc
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=24b4e9ee-f2c6-e46c-ef27-f911bdca53f8@mykolab.com \
--to=mstefani@mykolab.com \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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).