From: Karl Williamson <public@khwilliamson.com>
Date: Mon, 2 Sep 2013 17:17:13 +0000 (-0600)
Subject: toke.c: Clarify comment
X-Git-Tag: upstream/5.20.0~2037
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a96035c56e6096e8091826002c1d47a0595502f0;p=platform%2Fupstream%2Fperl.git

toke.c: Clarify comment
---

diff --git a/toke.c b/toke.c
index d6df9ed..01073d5 100644
--- a/toke.c
+++ b/toke.c
@@ -9389,9 +9389,14 @@ S_scan_ident(pTHX_ char *s, const char *send, char *dest, STRLEN destlen, I32 ck
 	   s++;
     }
 
-/*  \c?, \c\, \c^, \c_, and \cA..\cZ minus the ones that have traditionally
- *  been matched by \s on ASCII platforms, are the legal control char names
- *  here, that is \c? plus 1-32 minus the \s ones. */
+/* Is the byte 'd' a legal single character identifier name?  'u' is true
+ * iff Unicode semantics are to be used.  The legal ones are any of:
+ *  a) ASCII digits
+ *  b) ASCII punctuation
+ *  c) When not under Unicode rules, any upper Latin1 character
+ *  d) \c?, \c\, \c^, \c_, and \cA..\cZ, minus the ones that have traditionally
+ *     been matched by \s on ASCII platforms.  That is: \c?, plus 1-32, minus
+ *     the \s ones. */
 #define VALID_LEN_ONE_IDENT(d, u) (isPUNCT_A((U8)(d))                       \
                                    || isDIGIT_A((U8)(d))                    \
                                    || (!(u) && !isASCII((U8)(d)))           \