On Sun, 28 Mar 2021, Markus Elfring wrote:
> >> Would you like to help any more with attempts to achieve support for
> >> a transformation pattern like “#define ⇒ enum” according to the semantic
> >> patch language?
> >> https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/981
> >> https:/
On Sun, 28 Mar 2021, Markus Elfring wrote:
> > And what is the problem here?
>
> Would you like to discuss further software development ideas
> according to another SmPL script example like the following?
The following looks like what one might want to do to find #defines that
are near each oth
On Sun, 28 Mar 2021, Markus Elfring wrote:
> >> Another SmPL script example:
> >>
> >> @display2@
> >> identifier i;
> >> expression e;
> >> @@
> >> *#define i e
> >>
> >>
> >> elfring@Sonne:~/Projekte/Coccinelle/janitor> spatch
> >> show_define_usage2.cocci /usr/include/pipewire-0.3/pipewire/c
On Sun, 28 Mar 2021, Markus Elfring wrote:
> >> @display@
> >> @@
> >> *#define
> >
> > Obviously this doesn't work. Just like
> >
> > @@
> > @@
> > *if
> >
> > doesnt' work.
>
> Can it become possible to find such key words in the source code
> (by such SmPL search approaches)?
No. As has be
On Sun, 28 Mar 2021, Markus Elfring wrote:
> > If you find that something does not work satisfactorily, propose a
> > semantic patch and show what doesn't work.
>
> @display@
> @@
> *#define
Obviously this doesn't work. Just like
@@
@@
*if
doesnt' work.
> > I'm not going to try to solve a p
On Sun, 28 Mar 2021, Markus Elfring wrote:
> > Probably the simplest is to put the names of the header files in a file,
> > eg find . -name "*h" > header_list, and then give the arguement
> > --file-groups header_list to Coccinelle.
>
> How are the chances to add support for another program opti
On Sun, 28 Mar 2021, Markus Elfring wrote:
> >> https://github.com/coccinelle/coccinelle/issues/139
> >
> > I looked at the link, but there is no concrete example of something that
> > does not work, so I have no idea what the problem is.
>
> You expressed another bit of better understanding of
On Sun, 28 Mar 2021, Markus Elfring wrote:
> Hello,
>
> Will the software development interests ever evolve in ways so that #define
> directives
> can be replaced with the help of the semantic patch language for special
> source code
> analysis and transformation approaches?
> https://github.
On Sun, 28 Mar 2021, Markus Elfring wrote:
> Hello,
>
> The Coccinelle software can search for header files in addition to source
> files
> if the option “--include-headers” was specified.
> https://github.com/coccinelle/coccinelle/blob/287374196da8c7cfd169e721a2d23f1e462422f1/docs/manual/spatc
Hello,
Will the software development interests ever evolve in ways so that #define
directives
can be replaced with the help of the semantic patch language for special source
code
analysis and transformation approaches?
https://github.com/coccinelle/coccinelle/issues/139
Regards,
Markus
Hello,
The Coccinelle software can search for header files in addition to source files
if the option “--include-headers” was specified.
https://github.com/coccinelle/coccinelle/blob/287374196da8c7cfd169e721a2d23f1e462422f1/docs/manual/spatch_options.tex#L43
How can it be achieved that only header
Hello,
I am attempting to create a coccinelle script that will detect possibly buggy
usage of the bitwise operators where integer promotion may result in bugs,
usually due to sign extension.
I know this script needs a lot more work, but I am just beginning to learn the
syntax of coccinelle. At th
12 matches
Mail list logo