<div dir="ltr"><div dir="ltr">On Mon, Oct 28, 2019 at 9:39 AM Mathias Stearn via Core <<a href="mailto:core@lists.isocpp.org">core@lists.isocpp.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">Is it just uppercase letters in the basic source character set, or anything considered an uppercase letter in the universal character set after phase 1 transcoding and universal-character-name resolution? Or is there some other definition of uppercase?</div></div></div></blockquote><div><br></div><div>My interpretation:</div><div><br></div><div>* We don't resolve universal-character-names; rather, we *form* them. (Eg, int façade; is converted into int fa\u00e7ade;) So for example _Ç becomes _\u00c7, which doesn't start with an underscore followed by an uppercase letter (it's an underscore followed by a slash).<br></div><div>* Unicode (to which we have a normative reference) defines uppercase, and we follow that, but we happen to only ever apply it to the basic source character set because of the above rewriting.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><div>I have a slight preference for restricting to just A-Z so that it doesn't require humans or tools to consult the unicode data tables to decide if an identifier is safe to use.</div></div></div></div></div></blockquote><div><br></div><div>Regardless of how we express the rule, I agree with this direction.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><div>Proposed resolution:</div><div><br></div><div>Replace [lex.names]/3.2 with:</div><div><br></div><div>Each identifier that contains a double underscore __ or begins with an underscore followed by an uppercase <del>letter</del><ins><i>nondigit</i></ins> is reserved to the implementation for any use.</div></div></div></div></div></blockquote><div><br></div><div>... and I think this is a fine wording improvement, whether or not we think it's formally necessary.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr"><div><div>Alternatively we could either create a new grammar production for uppercase <i>nondigit</i>s, or just say something like "one of the universal characters in the range 0041-005A (A-Z)"</div><div><br></div><div><br></div></div></div>
</div></div>
_______________________________________________<br>
Core mailing list<br>
<a href="mailto:Core@lists.isocpp.org" target="_blank">Core@lists.isocpp.org</a><br>
Subscription: <a href="https://lists.isocpp.org/mailman/listinfo.cgi/core" rel="noreferrer" target="_blank">https://lists.isocpp.org/mailman/listinfo.cgi/core</a><br>
Link to this post: <a href="http://lists.isocpp.org/core/2019/10/7541.php" rel="noreferrer" target="_blank">http://lists.isocpp.org/core/2019/10/7541.php</a><br>
</blockquote></div></div>