Sorry for the confusion. Ideally most of the syntax described will
beavailable in both pregexp and regexp mode, but "\\X" and
"\\u{E0}"should probably be restricted to pregexp only.
> To add to my confusion, your original email mentioned #px"n", which>
> currently matches a backslash followed
Sorry for the butchered e-mail, I was quite careful to send it in
plain textmode, so I don't know how that happened.
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
It was brought up that my explanation was confusing, and I agree it is.
So I'll try again. The following should return #t:
(regexp-match? #px"\\u{E0}" "\u00E0")(regexp-match? "\\X"
"\u00E0")(regexp-match? "\\u00E0" "\u00E0")(regexp-match? "\\x00"
"\x00")(regexp-match? "\\n" "\n")(regex
Racket pregexp syntax is currently missing the following:
#px"X"-> a single Unicode grapheme
#px"u[a-fA-F0-9]{4}" -> hexidecimal Unicode escapes
#px"u\\{[a-fA-F0-9]{1,4}\\}" -> hexidecimal Unicode escapes
#px"x[a-fA-F0-9]{2}" -> \x escapes
4 matches
Mail list logo
