Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note to [re.traits] about non-standard character classes are allowed #206

Open
jwakely opened this issue Sep 30, 2013 · 1 comment
Open
Labels
lwg Issue must be reviewed by LWG.

Comments

@jwakely
Copy link
Member

jwakely commented Sep 30, 2013

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.

@jensmaurer
Copy link
Member

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.

@jensmaurer jensmaurer added the lwg Issue must be reviewed by LWG. label Nov 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lwg Issue must be reviewed by LWG.
Projects
None yet
Development

No branches or pull requests

2 participants