All of lore.kernel.org
 help / color / mirror / Atom feed
From: devel.fx.lebail@orange.fr (Francois-Xavier Le Bail)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Question about a not made change
Date: Mon, 27 Nov 2017 10:49:11 +0100	[thread overview]
Message-ID: <f1f1bccb-24fe-3a75-05e8-c6531faedcb9@orange.fr> (raw)
In-Reply-To: <alpine.DEB.2.20.1711251431290.2096@hadrien>

On 25/11/2017 14:32, Julia Lawall wrote:
> 
> 
> On Sat, 25 Nov 2017, Francois-Xavier Le Bail wrote:
> 
>> On 25/11/2017 08:44, Julia Lawall wrote:
>>> On Sat, 25 Nov 2017, Francois-Xavier Le Bail wrote:
>>>> I try the following patch:
>>>> -----
>>>> @@
>>>> u_char *p;
>>>> expression n;
>>>> @@
>>>> ND_PRINT(
>>>> ...,
>>>> -p[n]
>>>> +EXTRACT_U_1(p + n)
>>>>  )
>>>> -----
>>>> on the following (minimized) code:
>>>> -----
>>>> int main()
>>>> {
>>>>         u_char *p;
>>>>         ND_PRINT(ndo, ": %02x %02x", p[1], p[2]);
>>>>
>>>>         return 0;
>>>> }
>>>> -----
>>>> I got:
>>>> -----
>>>> +++ /tmp/cocci-output-1795-a34831-main.c
>>>> @@ -1,7 +1,7 @@
>>>>  int main()
>>>>  {
>>>>         u_char *p;
>>>> -       ND_PRINT(ndo, ": %02x %02x", p[1], p[2]);
>>>> +       ND_PRINT(ndo, ": %02x %02x", p[1], EXTRACT_U_1(p + 2));
>>>>
>>>>         return 0;
>>>>  }
>>>> -----
>>>> Why the first p[1] is not change to EXTRACT_U_1(p + 1)?
>>>>
>>>> Did I miss something obvious?
>>>
>>> Yes :)  There is no ,... after your change, so you only perform the change
>>> when it is the last argument.
>>
>> Thus, going closer my original problem, where ND_PRINT is a macro which requires double parenthesis,
>> I try :
>> -----
>> @@
>> u_char *p;
>> expression n;
>> @@
>> ND_PRINT((
>> ...,
>> -p[n]
>> +EXTRACT_U_1(p + n)
>> ,...
>>  ))
>> -----
>> I got:
>> -       ND_PRINT((ndo, ": %x %x %x %x", p[1], p[2], p[3], p[4]));
>> +       ND_PRINT((ndo, ": %x %x %x %x", p[1], p[2], EXTRACT_U_1(p + 3), p[4]));
>> -----
>>
>> Another thing I miss?
> 
> I'm not sure that the double parens are well supported.  Try <+... ...+>
> around your specific change, but I don't know if it will work.

It's works, Thank you !

-- 
Francois-Xavier

      reply	other threads:[~2017-11-27  9:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25  7:38 [Cocci] Question about a not made change Francois-Xavier Le Bail
2017-11-25  7:44 ` Julia Lawall
2017-11-25  7:54   ` Francois-Xavier Le Bail
2017-11-25 12:26   ` Francois-Xavier Le Bail
2017-11-25 13:32     ` Julia Lawall
2017-11-27  9:49       ` Francois-Xavier Le Bail [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1f1bccb-24fe-3a75-05e8-c6531faedcb9@orange.fr \
    --to=devel.fx.lebail@orange.fr \
    --cc=cocci@systeme.lip6.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.