From: picca <picca@debian.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@inria.fr
Subject: Re: [cocci] Bug dans la parseur de coccinelle ?
Date: Thu, 12 Nov 2026 15:51:53 +0100 [thread overview]
Message-ID: <b4048ae138808c03693d43cd183c7ab8@debian.org> (raw)
In-Reply-To: <b225b777-9216-635a-76b8-fc46f6d6a3@inria.fr>
> Alternatively, if it's easier, could you retry after removing the
> following line from standard.h:
>
> #define INLINE inline
>
> That looks problematic, but I'm not sure that that definition should be
> applied if there is not another parsing error in your code.
>
> julia
It works without this INLINE
-----------------------------------------------------------------------
Finished
-----------------------------------------------------------------------
diff =
--- ana_read.c
+++ /tmp/cocci-output-2311372-3e6202-ana_read.c
@@ -646,7 +646,7 @@ static void read_spec(Ana *ana)
sprintf(STRING,"x title %s break",XCOLNAME);
put_command(&ana->rod.menu, STRING);
- plotxye(x,y,e,1);
+ plotxye(&ana->pg, &ana->rod.menu, x, y, e, 1);
}
for(i = 0; i < ncolumns; i++)
@@ -988,7 +988,7 @@ static void read_srs(Ana *ana, int versi
{
sprintf(STRING,"x title %s break",XCOLNAME);
put_command(&ana->rod.menu, STRING);
- plotxye(x,y,e,1);
+ plotxye(&ana->pg, &ana->rod.menu, x, y, e, 1);
}
/* Get column number of y values */
next prev parent reply other threads:[~2026-11-12 14:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:34 [cocci] Bug dans la parseur de coccinelle ? picca
2026-11-12 10:40 ` Julia Lawall
2026-11-12 10:47 ` picca
2026-11-12 12:12 ` Victor Gambier
2026-11-12 12:26 ` picca
2026-11-12 12:29 ` Victor Gambier
2026-11-12 12:36 ` picca
2026-11-12 14:10 ` picca
2026-11-12 14:43 ` Julia Lawall
2026-11-12 14:44 ` Julia Lawall
2026-11-12 12:36 ` Markus Elfring
2026-11-12 12:41 ` picca
2026-11-12 14:51 ` picca [this message]
2026-11-12 14:55 ` Julia Lawall
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=b4048ae138808c03693d43cd183c7ab8@debian.org \
--to=picca@debian.org \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.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.