>> I assume that it is still a configuration challenge to get rid of a message >> like >> "__dest: present in 16 parsing errors" for the source file "string.h". > > You have to look at the context of __dest to see how it does not follow the > normal C grammar. Often the problem is not the specified token, but something > nearby that causes the parser to interpret the specified token in the wrong > way.
Would you spot corresponding improvements easier than me from the processing mode "-verbose_parsing" of the tool "spatch"? Regards, Markus _______________________________________________ Cocci mailing list [email protected] http://lists.diku.dk/mailman/listinfo/cocci (Web access from inside DIKUs LAN only)
