summaryrefslogtreecommitdiff
path: root/regen
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2011-02-06 21:22:32 -0700
committerKarl Williamson <public@khwilliamson.com>2011-02-14 08:41:36 -0700
commit33e4950cb5482d2816edbeee1e59d4323dba498c (patch)
tree4c67b07b35d69680fada3074727373fd98323d21 /regen
parent43322ea3ef667fae3d18a7fe6d5299b64ca1f354 (diff)
downloadperl-33e4950cb5482d2816edbeee1e59d4323dba498c.tar.gz
Revert "l1_char_class_tab.h: Remove multi-char fold targets"
This reverts commit 88c8c9616516015e2fe0b502cdb92dc4efcc0c10. It turns out that these multi-char fold targets are now needed; In a future commit, I plan to compile in the dozen or so rules that are needed to avoid a Latin1-only regex from having to go out to the utf8 tables to avoid the performance penalty; or calling code can use the also forthcoming 'use re "/aa"'.
Diffstat (limited to 'regen')
-rw-r--r--regen/mk_PL_charclass.pl2
1 files changed, 1 insertions, 1 deletions
diff --git a/regen/mk_PL_charclass.pl b/regen/mk_PL_charclass.pl
index b616f85748..5b2cca70f1 100644
--- a/regen/mk_PL_charclass.pl
+++ b/regen/mk_PL_charclass.pl
@@ -71,7 +71,7 @@ while (<$fh>) {
my $from = hex $hex_from;
# Perl only deals with C and F folds
- next if $fold_type ne 'C'; # Not currently used: && $fold_type ne 'F';
+ next if $fold_type ne 'C' and $fold_type ne 'F';
# Get each code point in the range that participates in this line's fold.
# The hash has keys of each code point in the range, and values of what it