On Mar 17, 2010, at 9:28 AM, Garrett D'Amore wrote:
> I think we were still waiting for Glenn's reply that he was
> satisfied. We still have not received a +1 from another member.
>
> Glenn, are you satisfied with responses to your concerns?
Oops, sorry. The case inadvertently fell off my radar screen. See
comments interleaved below.
> On 03/17/10 09:10 AM, ????? ???????????? wrote:
>> Is this case now approved?
>>
>> Olga
>>
>> 2010/3/5 ????? ????????????<olga.kryzhanovska at gmail.com>:
>>
>>> 2010/3/2 ????? ????????????<olga.kryzhanovska at gmail.com>:
>>>
>>>> On Tue, Mar 2, 2010 at 10:44 PM, Glenn Skinner<glenn.skinner at covad.net
>>>> > wrote:
>>>>
>>>>> On Mar 2, 2010, at 12:55 PM, Garrett D'Amore - sun microsystems
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Interface Stability Description
>>>>>> --------- --------- -----------
>>>>>> /usr/bin/xgrep Committed xgrep command
>>>>>> ksh93 'xgrep' built in Committed xgrep command
>>>>>>
>>>>> Before I give this case my +1, I have some questions:
>>>>>
>>>>> The case's specification should define the syntax of the regular
>>>>> expressions
>>>>> the utility accepts. I suspect that the variants requested by
>>>>> the -E, -F,
>>>>> -G, and -P flags can be handled with references to the
>>>>> corresponding man
>>>>> pages. But what is the specification for -X mode REs (including
>>>>> the
>>>>> semantics of alternation and conjunction)?
>>>>>
>>>> -X is like POSIX grep -E (egrep) but adds& as AND operator and !
>>>> as
>>>> NOT operator.
It's typical for man pages for grep variants to have a subsection
called "REGULAR EXPRESSIONS" whose contents lay out the rules for the
syntax of the REs the utility accepts and of how matching works. I'm
looking for something similar here. (Some questions I'd hope the
section would answer: What are the precedences of the '&' and '!"
operators? When the '&' operator is used, if there's more than one
common substring matched by its left and right hand operands, which
one wins? Can precedences be overridden by using parentheses to group
sub-expressions?)
Stated differently, the spec should contain enough information to
allow someone using xgrep to construct and use a regular expression
for a given purpose.
(Stated differently still, I want to know what I'm buying.)
On Mar 2, 2010, at 2:19 PM, ????? ???????????? wrote:
> On Tue, Mar 2, 2010 at 10:44 PM, Glenn Skinner <glenn.skinner at covad.net
> > wrote:
>
>> What is the default for the -H, -h option pair? The traditional grep
>> utility only prefixes matches with file names when there's more
>> than one
>> source file. Is there a way to request compatibility with that
>> behavior?
>> (I think there should be.)
>
> This is already the default.
>
> Try:
> builtin xgrep
> xgrep ksh /etc/profile /etc/profile
Just to make sure I understand, if neither of -h nor -H is given,
xgrep will only include file names when there's more than one file
named on the command line. If one of -h or -H is given, it
unconditionally (respectively) doesn't or does include them. Do I
have that right? (If so, it would be good if the man page were to
state this behavior explicitly.)
>> If conflicting options are given on the command line, which one
>> wins? The
>> first, the last, is it an error?
>
> Should be an error unless POSIX defines it else for this option.
Your answer is ambiguous. I'd like a definite answer. (I'm pushing
on this one because "last one wins" is useful for defining aliases;
the alias definition includes one of a pair of conflicting options,
but an invocation of the alias can still override by explicitly
mentioning the other option of the pair.)
-- Glenn
