Re: [RFC] Improved handling of member access operators with SmPL expression variables

[Markus Elfring]

>> Another SmPL script example:
>> @my_test@
>> expression hint;
>> @@
>> *hint->hint
>>
>>
>> Questionable test result (also according to the software combination “Coccinelle 1.3.2”):
>> Markus_Elfring@Sonne:…/Projekte/Coccinelle/Probe> spatch --parse-cocci show_expression_for_same_member_name.cocci
>> …
>> minus: parse error:
>>   File "show_expression_for_same_member_name.cocci", line 4, column 7, charpos = 37
>>   around = 'hint',
>>   whole content = *hint->hint
…
> They will not improve.  …
>                   It is not in the spirit of the language.
* Under which circumstances would you get into the mood to explain the reasons for
  the presented error message?

* Can collateral evolution become more interesting?

* How many member names can be handled by bigger SmPL rules?


Regards,
Markus