diff options
author | Karl Williamson <khw@cpan.org> | 2015-09-09 12:43:15 -0600 |
---|---|---|
committer | Karl Williamson <khw@cpan.org> | 2015-09-11 12:07:37 -0600 |
commit | 0f0eec8fa0e9c6558ae31d368ff8b2c87314deee (patch) | |
tree | aa462ad86031afb0a84865256a4c0c999b132c11 | |
parent | 6b5cf123f371e012d9812b37b13d50c6e06bf555 (diff) | |
download | perl-0f0eec8fa0e9c6558ae31d368ff8b2c87314deee.tar.gz |
regcomp.c: Fix, clarify comments
-rw-r--r-- | regcomp.c | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -12285,7 +12285,7 @@ S_regatom(pTHX_ RExC_state_t *pRExC_state, I32 *flagp, U32 depth) * string's UTF8ness. The reason to do this is that EXACTF is not * trie-able, EXACTFU is. * - * Similarly, we can convert EXACTFL nodes to EXACTFU if they + * Similarly, we can convert EXACTFL nodes to EXACTFLU8 if they * contain only above-Latin1 characters (hence must be in UTF8), * which don't participate in folds with Latin1-range characters, * as the latter's folds aren't known until runtime. (We don't @@ -12724,7 +12724,7 @@ S_regatom(pTHX_ RExC_state_t *pRExC_state, I32 *flagp, U32 depth) * we have an array that finds its fold quickly */ *(s++) = (char) ender; } - else { /* FOLD and UTF */ + else { /* FOLD, and UTF (or sharp s) */ /* Unlike the non-fold case, we do actually have to * calculate the results here in pass 1. This is for two * reasons, the folded length may be longer than the |