According to Geoff Hutchison:
> At 3:53 PM -0500 4/10/00, Gilles Detillieux wrote:
> >Yes, the "NEAR" operator you suggested would be useful for a fuzzy
> >phrase search, but until then, I think it makes sense to turn off the
> >fuzzy matching for phrases. You'll still need to do something about
> >that infinite loop, though. It seems to me that punctuation in a phrase
> >should be ignored, and not parsed as expression syntax.
>
> Well... A '(' character at this point in the code is no longer
> punctuation. (This is why the parser dies.) Obviously I'll test out
> the fix carefully, but I don't think it will be possible to get an
> infinite loop this way. For example, anything besides a '(' character
> shouldn't provide problems at all since it's ignored by the parser.
>
> Granted, the parser shouldn't be using characters at all since
> someone searching for "&test" doesn't want that confused with "AND
> test" but IMHO, that's *way* beyond a simple fix.
Again, I'm probably oversimplifying, but couldn't you just strip out or
ignore parentheses, boolean operators, or any punctuation for that matter,
within double quotes, when initially scanning the "allWords" string in
setupWords() ?
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
