Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH 22/24] membarrier.2: Note that glibc does not provide a
 wrapper
To:     "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc:     linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
        mtk.manpages@gmail.com
References: <20200927054657.ea2zaiesle6hwjit@localhost.localdomain>
 <562859fd-6740-1068-d9d0-9562140cec33@gmail.com>
 <20200928125227.yr2ugl23ib6mid76@localhost.localdomain>
From:   Alejandro Colomar <colomar.6.4.3@gmail.com>
Message-ID: <5d4f71a6-8a5e-c683-fcbd-b5453435d736@gmail.com>
Date:   Mon, 28 Sep 2020 15:33:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <20200928125227.yr2ugl23ib6mid76@localhost.localdomain>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 2020-09-28 14:52, G. Branden Robinson wrote:
 > At 2020-09-27T22:05:14+0200, Alejandro Colomar wrote:
 >> Hi Branden,
 >>
 >> * G. Branden Robinson via linux-man:
 >>
 >> 1)
 >>
 >>> .EX
 >>> .B int fstat(int \c
 >>> .IB fd , \~\c
 >>> .B struct stat *\c
 >>> .IB statbuf );
 >>> .EE
 >>
 >> 2)
 >>
 >>> .EX
 >>> .BI "int fstat(int " fd ", struct stat *" statbuf );
 >>> .EE
 >>
 >> 3)
 >>
 >>> .EX
 >>> .BI "int fstat(int\~" fd ", struct stat *" statbuf );
 >>> .EE
 >>
 >> I'd say number 2 is best.  Rationale: grep :)
 >> I agree it's visually somewhat harder, but grepping is way easier.
 >
 > I don't see how (2) is any tougher to grep than (3)...?
 >
 > If I'm grepping, I'm usually concerned with things like
 > variable/function names and not with punctuation, so if I were grepping
 > for the above function signature I'd probably write:
 >
 > $ grep 'fstat.*fd.*statbuf' man2/*
 >
 > ...which would catch either of the above just fine.
 >
 > Am I missing something?
 >
 > Regards,
 > Branden
 >

There are a few cases:  if I want to find declarations of type int,
I'd start with:

$ grep -rn "int\s"

or something like that.  "int\~" would break the ability to do that.

Regards,
Alex