To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=15666
------- Additional comments from [EMAIL PROTECTED] Tue Feb 14 09:36:40 -0800 2006 ------- > This is a good first step for the RE functionality. It get's us passed the > current limitations. Thanks. I just relized that in this code, registers usable in the replace string are limited to 1-digit, so 9 submatches. This could be extended to 2-or-more-digit registers, but would complicate the code. I guess 9 is a plenty. > I am not sure what you are saying about the & substitution versus using \0. > & in the replace field should return the entire matched string from the > search field. Of course it's possible to reimplement the & as special character. Users that are used it this way wouldn't have to change over, I don't see a reason for having & match the whole string. \0 for all and \1-\9 is more straightforward (to code an to learn). > If OO is using a broken version of GNU Regular expressions Er no, I didn't write broken - it's modified (mostly to make it use classes). What I meant with "misses some advanced features" is the lib misses them - also in the FSF's original version. If some more PCRE functionality is required it will be harder to implement since registers have already been supported and used internally. More than that, in my patch actually only *one* line of code was added to the regex code, the rest is in OOo code. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
