You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the acceptance of LWG DR 2018 the spec for isctype still doesn't allow for additional implementation-defined character classes, because "the result is
determined as if by ..." doesn't allow for handling additional special
cases similar to how underscores are handled.
A note on isctype saying "implementations are permitted to support additional character classes recognized by lookup_classname()" might be enough, given that lookup_classname() has normative wording saying "at least" the named classes will be recognized.
The text was updated successfully, but these errors were encountered:
I can't see how the "as if by" wording in LWG 2018 would allow for implementation-defined character classes here, since lookup_classname() is only called for a specified class.
@jwakely: This looks like (another) LWG issue to me, if you want to enable implementation-defined character classes here.
With the acceptance of LWG DR 2018 the spec for
isctype
still doesn't allow for additional implementation-defined character classes, because "the result isdetermined as if by ..." doesn't allow for handling additional special
cases similar to how underscores are handled.
A note on
isctype
saying "implementations are permitted to support additional character classes recognized bylookup_classname()
" might be enough, given thatlookup_classname()
has normative wording saying "at least" the named classes will be recognized.The text was updated successfully, but these errors were encountered: