cocci.inria.fr archive mirror
 help / color / mirror / Atom feed
From: Thomas Adam <thomas@xteddy.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Wolfram Sang <wsa@kernel.org>, Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Replacing a struct member with a function call
Date: Mon, 15 Mar 2021 00:43:07 +0000	[thread overview]
Message-ID: <CAOhcEPZx4tNocG4TJvQKg_6e6kyJPbWGtj52TaGhJqHD36ZfYw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2103141016010.2986@hadrien>

Hello,

I can see I was as clear as mud with my explanation -- apologies for
that, so let me try again.

In my original example:

struct monitor {
    struct {
        int width;
        int height
    } virtual;
};

... the members width and height aren't required any more, as they're
actually computable generically, and don't belong in that struct.
Instead, I have separate functions which can provide those values.

So where I have in code, statements such as:

struct monitor *m = this_monitor();
int foo = m->virutal.width;

I want to be able to substitute "m->virtual.width" with a function
call "get_width()" -- which does not involve "struct monitor" at all.
Indeed, the semantic patch I'm trying to apply now looks like this:

@@
struct monitor *m;
@@

- m->virtual.width;
+ get_width();

... and although spatch doesn't tell me of any errors, when I run it
over my codebase, no modifications are made.  So clearly I'm still
doing something wrong.  At the point, I have some questions:

1.  Given the inner struct "virtual" inside of "struct monitor", is it
correct that spatch would understand:

m->virtual.width;

... or do I need to declare "virtual" as some expression or
identifier?  I did try:

@@
struct monitor *m;
expression virtual;
@@

- m->virtual.width;
+ get_width();

... but this results in an error.

2.  Do I need to declare "virtual" as a struct in its own right
somehow?  If so, it's not immediately obvious if this should be the
case or how to do it.

I hope I'm making some sense here -- apologies if not, and if I need
to expand upon anything further, do please let me know.

Essentially, it seems to me as though the inner struct "virtual" isn't
being declared as a valid type which spatch is understanding, and this
is why things aren't working how I'd like.

Again, thanks ever so much for you time -- everyone's been very
helpful to me in the past, and I've found coccinelle to be invaluable
to making sweeping code changes, as well as bug-fixes on my codebase,
so thanks to everyone involved in this project.  It's invaluable!

Kindly,
Thomas

On Sun, 14 Mar 2021 at 09:16, Julia Lawall <julia.lawall@inria.fr> wrote:
>
>
>
> On Sun, 14 Mar 2021, Wolfram Sang wrote:
>
> >
> > > @@
> > > type M;
> >
> > This?
> >
> > struct monitor* m;
> >
> > > @@
> > > - m->virtual.width;
> > > + get_monitor_width();
>
> I guess that m should be somewhere in teh call to get_monitor_width too?
>
> julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2021-03-15  0:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14  0:55 [Cocci] Replacing a struct member with a function call Thomas Adam
2021-03-14  6:10 ` Wolfram Sang
2021-03-14  9:16   ` Julia Lawall
2021-03-15  0:43     ` Thomas Adam [this message]
2021-03-15  6:38       ` Julia Lawall
2021-03-16  2:48       ` Mansour Moufid
2021-03-16  7:20         ` Julia Lawall
2021-03-18 18:19           ` Thomas Adam

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=CAOhcEPZx4tNocG4TJvQKg_6e6kyJPbWGtj52TaGhJqHD36ZfYw@mail.gmail.com \
    --to=thomas@xteddy.org \
    --cc=cocci@systeme.lip6.fr \
    --cc=julia.lawall@inria.fr \
    --cc=wsa@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).