Coccinelle Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: wagi@monom.org (Daniel Wagner)
To: cocci@systeme.lip6.fr
Subject: [Cocci] gboolean -> bool conversion
Date: Fri, 12 Jul 2013 08:55:06 +0200	[thread overview]
Message-ID: <51DFA84A.4050805@monom.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1307111451080.2253@hadrien>

Hi Julia,

On 07/11/2013 03:07 PM, Julia Lawall wrote:
>> I am pondering if it would be possible to say
>>
>> - gboolean
>> 	when != 'static gboolean func(gpointer)'
>> + bool
>
> No, this is not possible.  Is the idea that you don't want to change the
> return type of a static function?  Then you can record the position of the
> gbooleans that you don't want to change, and only change the others.

It is so obvious when you explain it. Thanks a lot.

> An example is as follows:
>
> @keep@
> identifier f;
> position p;
> typedef	gpointer;
> identifier i;
> @@
>
> static gboolean at p f(gpointer i)	{ ... }
>
> @@
> typedef bool;
> position p != keep.p;
> @@
>
> - gboolean at p
> + bool
>

With some small modification this works fine now.

The only outstanding problem I'd like to address is patching the 
function calls.

Let's say I have this deceleration (which will be changed by the above
rules):

	int foo(gboolean b);

and some place I call then

	foo(FALSE);

This should be changed to

	foo(false);

> Note that you could never refer to
>
> static gboolean func(gpointer)
>
> because it is not a complete syntactic unit.  If you wanted to mention a
> prototype, you would need a ; after it.  If you wanted to mention the
> definition, then you need to put the complete definition, as shown above.

I see. Thanks again for explaining.

thanks
daniel

  reply	other threads:[~2013-07-12  6:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  8:17 [Cocci] gboolean -> bool conversion Daniel Wagner
2013-07-11  8:29 ` Julia Lawall
2013-07-11  9:07   ` Daniel Wagner
2013-07-11  9:57     ` Julia Lawall
2013-07-11  9:58     ` Daniel Wagner
2013-07-11 10:24       ` Julia Lawall
2013-07-11 11:17         ` Daniel Wagner
2013-07-11 12:17           ` Julia Lawall
2013-07-11 12:38             ` Daniel Wagner
2013-07-11 13:07               ` Julia Lawall
2013-07-12  6:55                 ` Daniel Wagner [this message]
2013-07-12  7:00                   ` Julia Lawall
2013-07-12  9:08                     ` Daniel Wagner
2013-07-16 14:21                     ` Daniel Wagner
2013-07-16 16:22                       ` Julia Lawall
2013-07-17  8:47                         ` Daniel Wagner
2013-07-17  9:01                           ` Julia Lawall
2013-07-17 14:58                             ` Daniel Wagner
2013-07-17 15:11                               ` Julia Lawall
2013-07-17 15:40                                 ` Daniel Wagner

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=51DFA84A.4050805@monom.org \
    --to=wagi@monom.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox