Thanks for your feedback. I’m looking forward to your counter-proposal that makes the Windows situation well-formed.
From: SG16 <firstname.lastname@example.org>
On Behalf Of Peter Bindels via SG16
Sent: 14 April 2021 15:24
To: Corentin Jabot <email@example.com>
Cc: Peter Bindels <firstname.lastname@example.org>; SG16 <email@example.com>
Subject: Re: [SG16] P2362R0 Make obfuscating wide character literals ill-formed
I value portable code highly. If we have known platforms, and a competing proposal that makes the Windows situation well-formed, it makes this an odd sell to me. I do not want a specification that requires code to compile on Unix and fail
on Windows, even if it is not currently according to spec and somehow unportable code.
Blocking multi-character literals, sure. Blocking some single-character literals as IFDR when they work fine on other platforms, that's just not right. I don't think I like either variant - making it ill-formed on Unix, or to allow it on
Unix while making it ill-formed on Windows.
Then I have the inverse problem, now we create code that is conditionally portable, and only ill-formed on Windows. That's horrible.
How is that worse that code that is well-formed everywhere but does the wrong thing on windows?
wchar_t was never portable