> On the other hand, do you really require E to be a pointer? > If you do that, it will have to find the type of E.
I suggest to reconsider this information. > If E refers to a structure field, then the type might not be available > in the current function, and you may need command line argments like > --all-includes or --recursive-includes. Will the software documentation need corresponding extensions for the safe application of the semantic patch language? Will the used data structure access operator like arrow or dot influence the interpretation of the software situation? > Is avoiding transforming the case where E is not verified > to be a pointer a concern? I would find it desirable to express constraints for pointer data types according to the applied programming interfaces. Regards, Markus _______________________________________________ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci