#13 Optionally Circumvent the Regex Crippler

open
nobody
None
5
2012-10-08
2004-12-14
Gunther Schadow
No

I felt this was too ridiculous having had all my regexes
working well from prior versions of Saxon (7.8), Java
supporting all those so well, and now suddenly having to
redo them just because XPath version of regex is so
crippled (e.g., no word boundary \b match, which is not
easy to replace).

So, I went in and created an option to allow full regexes.
This simply shortcuts the RegexTranslator function. The
command line option is:

-fullregex

and the FeatureKey is

http://saxon.sf.net/feature/allow-full-regex

Discussion

  • Michael Kay
    Michael Kay
    2004-12-14

    Logged In: YES
    user_id=251681

    Sorry, but I am not prepared to endorse changes that modify
    Saxon to be non-conformant with the W3C specifications. The
    W3C specifications define mechanisms for extensibility of
    the language, and we must live within these rules. If we
    want to allow a different regex syntax, the way to do it is
    through a different set of functions.

    Michael Kay

     


Anonymous


Cancel   Add attachments