On Mon, 10 Apr 2000, Gaillard Pierre-Olivier wrote:

> Such an expression creates an infinite loop in the parser (the parse
> function loops without consuming the opening parenthesis). I believe we

Yuck. Thanks for your report, that's quite helpful. Someone recently
reported the same thing, but didn't provide any details, so I couldn't
reproduce it. They sent it to me personally, so it didn't end up in
Jitterbug.

> 1) detect the syntax error in the phrase parser

Currently, the only way to detect a syntax error is to start parsing it
and discover a problem. This is one of the drawbacks to the current code.

> 2b) prevent the endings algorithm from rewriting phrases.

When I first put in the phrase code, it was supposed to turn off fuzzy
matching inside the phrase. It's entirely possible this has been messed up
along the way. My thought was this: if a user wants a phrase search, they
don't want a fuzzy phrase search. Do others think this makes sense?

I consider this a showstopper, so I'll see if I can fix this again. A
truly good fix will require a cleanup along the lines Andrew and I
discussed before. That will have to wait until after 3.2.0b2.

-Geoff


------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] 
You will receive a message to confirm this. 


Reply via email to