On 9/24/25 18:35, Hubert Tong via SG16 wrote:
> On Wed, Sep 24, 2025 at 2:04 AM Tom Honermann via SG16 <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> __
>
> SG16 will hold a meeting *today*, Wednesday, September 24th, at 19:30 UTC (timezone conversion <https://www.timeanddate.com/worldclock/converter.html?iso=20250924T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>).
>
> If you need a .ics file to import into your calendar, you can download it here <https://documents.isocpp.org/remote.php/dav/public-calendars/R7imgS2LJD9xfeWN/BD8B73CA-A2A2-45E0-A9AB-2946907DF646.ics?export>.
>
> The agenda is:
>
> * P3688R3: ASCII character utilities <https://wg21.link/p3688r3>.
>
> I am quite concerned with the paper. I find the `is_ascii_` naming to be semantically confusing. For especially the `char` overloads (and to a lesser extent, the `wchar_t` overloads), I feel that the paper proposes data-centric treatment and that the "text" interface is incongruous.

Are you saying that, for an EBCDIC platform, having this example:

  char c = 'A';
  bool b = is_ascii_alpha(c);

could be interpreted as asking the question "is this an ASCII letter",
where the answer is "no", because "A" is an EBCDIC letter?
(Instead, this should be a precondition violation because "c" is not
encoded in ASCII or a superset thereof.)

If that's not it, can you show an example with some narrative?

Jens