Hi,
I just cleaned out the bug database and discovered something nice. Peter D.
Gray <[EMAIL PROTECTED]> sent us a "hack" for changing the htdig URL
exclusion and limit attributes into full regexp.
The patches are fairly small--he introduces a minimal Regex class and then
changed the calls to StringMatch with calls to his Regex class. I'll send
the patches if anyone wants.
So here's a question... Do we want this full regex behavior? Do we want to
replace StringMatch with a regex class? The bonus would be full regex
support in a number of areas. People have particularly complained about the
restrict/exclude behavior in htdig and htsearch.
The negative is that we have to field problems with incorrect regex
(ew...), and we will probably have to work on the Regex class some. We also
have no idea if it would be faster/slower or use more/less memory than
StringMatch.
My feeling is we should play with it and see how it works performance-wise.
I don't think the changes would be significant to what's contributed.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
