C++ Logo

sg16

Advanced search

Re: D2626R0 charN_t incremental adoption: Casting pointers of UTF character types

From: Corentin <corentin.jabot_at_[hidden]>
Date: Wed, 3 Aug 2022 08:18:40 +0200
On Tue, Aug 2, 2022 at 6:31 PM Peter Bindels <peterbindels_at_[hidden]> wrote:

> 1. Add uint8_t, uint16_t and uint32_t to the table. May not exist, but it
> is ridiculous if those do not work.
>

Thanks, I updated the paper to explain that
charN_t is always defined to have a uint_leastN_t underlying representation,
on all platforms, so that's what the wording uses.
On platforms where they are defined (thankfully, the vast majority of them)
uintN_t are aliases of uint_leastN_t
So if they exist, they work.



> 2. Rephrase nuking. Try not to use war terms for programming language
> design.
>
> Rest lgtm.
>
> On Tue, Aug 2, 2022, 13:44 Corentin via SG16 <sg16_at_[hidden]>
> wrote:
>
>> Actually, I think this is certainly good enough for a first presentation.
>> Tom, could you schedule it whenever SG16 has time?
>>
>> Thanks,
>>
>> Corentin
>>
>> On Sat, Jul 30, 2022 at 8:16 PM Corentin <corentin.jabot_at_[hidden]>
>> wrote:
>>
>>> Early draft, feedback welcome.
>>>
>>> Thanks,
>>> Corentin
>>>
>>> https://isocpp.org/files/papers/D2626R0.pdf
>>>
>> --
>> SG16 mailing list
>> SG16_at_[hidden]
>> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>>
>

Received on 2022-08-03 06:18:52