aboutsummaryrefslogtreecommitdiffstats
path: root/Source/SPSQLTokenizer.l
diff options
context:
space:
mode:
authorMax <post@wickenrode.com>2015-02-01 20:19:52 +0100
committerMax <post@wickenrode.com>2015-02-01 20:19:52 +0100
commit60a5d64518f09af80059e2e293849ff6b0d6be75 (patch)
tree9e59d6560bcdf256d9fcb363cd93993c40ff3235 /Source/SPSQLTokenizer.l
parentc25bb060a197deecc79dac86e24df8246a87db71 (diff)
downloadsequelpro-60a5d64518f09af80059e2e293849ff6b0d6be75.tar.gz
sequelpro-60a5d64518f09af80059e2e293849ff6b0d6be75.tar.bz2
sequelpro-60a5d64518f09af80059e2e293849ff6b0d6be75.zip
Change lexer definition of high bytes.
flex does not(*) support UTF-8, therefore alpha [a-z_\.À-゚] has always been interpreted by flex as alpha [a-z_\.\xC3\x80-\xEF\xBE\x9F] I assume this is not what was indetend and the only reason it worked, is because C3 (195),BE (190) and 9F (159) are already covered by 80-EF (128-239). Incidentally this range would also cover the whole Unicode BMP in UTF8. This change should make it more obvious. (*) There were some patches in 2012 and 2014 but they don't seem to have been merged.
Diffstat (limited to 'Source/SPSQLTokenizer.l')
-rw-r--r--Source/SPSQLTokenizer.l2
1 files changed, 1 insertions, 1 deletions
diff --git a/Source/SPSQLTokenizer.l b/Source/SPSQLTokenizer.l
index f33d373d..5b08f312 100644
--- a/Source/SPSQLTokenizer.l
+++ b/Source/SPSQLTokenizer.l
@@ -50,7 +50,7 @@ size_t yyuoffset, yyuleng;
s [ \t\n\r]
dkey "delimiter"
scol ";"
-dval [!-゚]
+dval [!-\x7E\x80-\xEF]
compstart "begin"{s}
compend {s}"end"
%x comment