>> I tried three different orderings out for these position variables
>> in the meantime.
>>
>> Will the implementation be fixed for all affected software components anyhow?
>
> No.
I am still curious then under which circumstances this software will be
corrected.
Regards,
Markus
Variable find.p2 in duplicated_code cannot be used as both a position and
a constraint
>>>
>>> I think that you have to declare find.p1 and find.p2 on a subsequent line.
>>
>> I have observed the same error message then.
>
> Go back and read what I wrote.
I suggest to take another look
>> elfring@Sonne:~/Projekte/Coccinelle/janitor> spatch --parse-cocci
>> show_same_statements7.cocci
>> …
>> Variable find.p2 in duplicated_code cannot be used as both a position and a
>> constraint
>
> I think that you have to declare find.p1 and find.p2 on a subsequent line.
I have observed
On Sun, 14 Apr 2019, Markus Elfring wrote:
> > Use position variables and use a second rule that forces the positions to
> > be different. I already explained this.
>
> I suggest to take another look at the provided information.
>
> I have extended the analysis approach like the following.
>
>
> Use position variables and use a second rule that forces the positions to
> be different. I already explained this.
I suggest to take another look at the provided information.
I have extended the analysis approach like the following.
@find@
identifier work;
position p1, p2;
statement s1,
