According to Alexander Langer:
> Thus spake Gilles Detillieux ([EMAIL PROTECTED]):
>
> > exclude_urls: [/foo/[a-z]+[0-9][^abc]\.html] \
> > [/foo/[a-z]+[0-9][^abc]\.php]
>
> I'm now using
> [/phorum/list.php.f=[0-9][0-9]*&..*] \
> [/phorum/read.php.f=[0-9][0-9]*&i=[0-9][0-9]*&t=[0-9][0-9]*&..*]
>
> At least the first case seems to work.
> The second doesn't in some cases
> (it also includes URLs with e.g. i=1&t=2&a=3), but it at least is
> enough for now.
>
> Note that I replaced every "+" to special "*" and replaced the "?"
> with "." (could be the reason why it works now, I forgot about its
> possible special treatment).
I don't think the "?" has a special meaning, either in limited or extended
regular expressions. My understanding was it's taken literally.
> > On what system did you build htdig? What is the setting of HAVE_BROKEN_REGEX
> > in include/htconfig.h (defined or undefined)?
>
> I'm using
> FreeBSD hostname 4.3-STABLE FreeBSD 4.3-STABLE #0: Thu May 31
> 10:08:42 CEST 2001 root@hostname:/usr/obj/usr/src/sys/KERNCONF i386
>
> #define HAVE_BROKEN_REGEX 1
> ^^^ GRRR :-)
The HAVE_BROKEN_REGEX may not be as bad as it sounds. What it means is
that the GNU regex code bundled in with the htdig source won't peacefully
coexist with your system's C or C++ library, so htdig needs to use the
C library's regex functions. This commonly happens on BSD systems. It's
only a problem if your C library's regex functions are truly bad or broken,
but the configure test doesn't actually make that determination.
--
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
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
