
On 10. 02. 22 0:30, Inada Naoki wrote:
On Thu, Feb 10, 2022 at 3:49 AM Brett Cannon <brett@python.org> wrote:
On Wed, Feb 9, 2022 at 4:19 AM Petr Viktorin <encukou@gmail.com> wrote:
On 09. 02. 22 4:39, h.vetinari@gmx.com wrote:
That's an interesting idea -- what's keeping us from C11?
No one asking before, probably because we have been trying to get to C99 for so long. 😄
In other words: the main thing keeping us from C99 is MSVC support, and since that compiler apparently skipped C99, should we skip it as well?
If we think "C11 without optional features" is widely supported then I think that's a fine target to have.
For anyone not sure what's optional in C11, I found https://en.wikipedia.org/wiki/C11_%28C_standard_revision%29#Optional_feature... . Other than atomics being discussed on Discord for mimalloc, leaving those things out seem reasonable to me.
I like it. I want to use anonymous union. It makes complex structure like PyDictKeysObject simple a little.
I confirmed that XLC supports it. https://www.ibm.com/docs/en/xl-c-and-cpp-aix/13.1.3?topic=types-structures-u...
Ah, I've also wanted anonymous unions in the past! There's a little problem in that they're not valid in C++, so we can't have them in public headers. We'll need to mention C++ if we update the standard.