On Wed, Apr 28, 1999 at 09:44:24PM -0400, Geoff Hutchison wrote:
>
> 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.
>
Not surprizingly, I vote in favour of making the regex comparisons
the default behaviour once they have been tested.
I don't think (vigorous hand waving) that there will be any
performance degradation and it may even be faster, given that
the people who write the regex stuff spend a lot of time on
performance. For example, when the search string contains no
special characters, grep runs 3 times faster than fgrep on
my machine. There may be some additional memory
required.
Regards,
pdg
------------------------------------
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.
