On 28/04/2022 21.04, Steve Downey via SG16 wrote:
> There are 5 remaining mentions of Execution Character Set in the draft:

Did you check the C standard and the indirect impact it has
on C++, given that we inherit quite a few library functions
from C?

> [lex.charset] 6
> A literal encoding or a locale-specific encoding of one of the execution character sets ([character.seq]) encodes each element of the basic literal character set as a single code unit with non-negative value, distinct from the code unit for any other such element.
>
>
>
> Is it the set of all possible characters in any encoding that is supported?

No, it's "a[n] encoding", not several.

> While it's probably worthwhile not to break someone's existing C++ reference material, I'm not sure we have a crisp and clean definition here, nor am I sure that multibyte character should be tied to it?
>
> I don't have any concrete suggestions here, but I was trying to help someone else understand the new model, and they had questions that were harder to answer than I expected.

"Execution character set" is essentially what comes from your
current POSIX locale setting at runtime.

Jens