Project

Profile

Help

Patch #1409

closed

Optionally Circumvent the Regex Crippler

Added by Anonymous almost 20 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Internals
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Legacy ID:
sf-1085241
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

SourceForge user: gschadow

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


Files

Actions #1

Updated by Anonymous almost 20 years ago

SourceForge user: mhkay

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

Actions #2

Updated by Michael Kay over 11 years ago

Closed. There is now a (not well documented!) way of getting Saxon to accept native Java regular expressions, by including "!" at the end of the flags attribute. (I don' think it's tested, though).

Actions #3

Updated by Michael Kay over 11 years ago

  • Status changed from New to Closed

Please register to edit this issue

Also available in: Atom PDF