Roland Mainz wrote:
> Peter Memishian wrote:
>>  > Sometimes I wish "findunref" would support the "extended shell pattern
>>  > scheme" as used by AST tools and ksh93 (e.g. above line would be
>>  > ~"(Ei).*/.*README" (e.g. "Ei" means egrep-pattern, case insensitive))
>>
>> With the Mercurial conversion, it's been rewritten in Python, so that may
>> be easy to do.
> 
> If you do that please please follow the AST/ksh syntax (e.g. it wouldn't
> be good to have several variants of the same syntax), e.g. "~(" as
> prefix to indicate alternative pattern method, "<name>" as name of the
> method (currently supported by libast&&ksh93 are AFAIK "F"/"G"/"E" for
> fgrep/grep/egrep-like pattern (which support modifers "i" for
> case-insensitive matching and "l" and "r" for left and right anchors),
> "S" for shell pattern, "K" for korn shell pattern (both are the same),
> "P" for perl regular expressions and AFAIK there are a few undocumented
> methods, too ("A" is reversed for AmigaOS-like pattern)) and a closing
> ")" before the pattern itself.

As meem noted, findunref will be a Python script after we do the SCM 
Migration tools putback, but we won't be implementing this extended 
shell pattern matching as part of our project.

If you like, once we've putback - you can file a bug and submit a 
sponsor request to add this support.  It shouldn't be too difficult.

cheers,
steve

-- 
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to