summaryrefslogtreecommitdiff
path: root/toke.c
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2013-09-02 11:17:13 -0600
committerKarl Williamson <public@khwilliamson.com>2013-09-02 11:34:36 -0600
commita96035c56e6096e8091826002c1d47a0595502f0 (patch)
tree5698a24eced65229be25f8231dd5a2f0773ee607 /toke.c
parent7a258a813b64e345d010ffe1c16ce7e55e146e50 (diff)
downloadperl-a96035c56e6096e8091826002c1d47a0595502f0.tar.gz
toke.c: Clarify comment
Diffstat (limited to 'toke.c')
-rw-r--r--toke.c11
1 files changed, 8 insertions, 3 deletions
diff --git a/toke.c b/toke.c
index d6df9edaef..01073d5a67 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))) \