At Wed, 21 Feb 2001 14:12:51 +0900,
I wrote:
> At Wed, 21 Feb 2001 12:35:09 +0900,
> Daniel C. Sobral wrote:
> > I'm not familiar with find sources, but it seems to me you execute
> > regcomp() for each file name to be compared? If so... change that! :-)
> > Regcomp() does expensive setup so that regexec() can be run
> > inexpensively many times over.
>
> Indeed. I'll do it soon, thanks.
Updated.
http://people.FreeBSD.org/~knu/misc/find_regex.diff
> > You forgot -E (use extended regexp syntax), and the example you show
> > above is extended regexp syntax, not basic regexp syntax.
Well, it was added after I had posted the original article. The
latest one's find.1 mentions it.
.It Fl E
Interpret regular expressions followed by
.Ic -regex
and
.Ic -iregex
options as extended (modern) regular expressions rather than basic
regular expressions (BRE's). The
.Xr re_format 7
manual page fully describes both formats.
As for the syntax my examples conform to, I think they are valid both
for basic and extended.
True if the whole path of the file matches
.Ar pattern
using regular expression. To match a file named ``./foo/xyzzy'', you
can use the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not
``xyzzy'' or ``/foo/''.
Thanks for your suggestions.
--
/
/__ __ Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"We're only at home when we're on the run, on the wing, on the fly"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
