[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc00475c-47af-f9d9-fdb5-5a88d520e52a@gmail.com>
Date: Mon, 28 Sep 2020 16:42:57 +0200
From: Alejandro Colomar <colomar.6.4.3@...il.com>
To: David Laight <David.Laight@...LAB.COM>,
"G. Branden Robinson" <g.branden.robinson@...il.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-man@...r.kernel.org" <linux-man@...r.kernel.org>,
"mtk.manpages@...il.com" <mtk.manpages@...il.com>
Subject: Re: [PATCH 22/24] membarrier.2: Note that glibc does not provide a
wrapper
On 2020-09-28 15:48, G. Branden Robinson wrote:
>> 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.
>
> That would, among more obscure cases, miss the style of function
> declaration used by people who get along without ctags:
>
> static int
> my_little_function(int foo, char bar)
>
> So I would tend to use grep 'int\>' to match a word boundary instead of
> a whitespace character.
>
> Regards,
> Branden
>
On 2020-09-28 16:31, David Laight wrote:
> From: Alejandro Colomar
>> Sent: 28 September 2020 14:33
> ...
>> 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.
>
> The 'word markers' \< and \> are your friends; look for "\<int\>".
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
Thank you both, I didn't know about those.
Regards,
Alex
Powered by blists - more mailing lists