On Thu, Jun 06, 2019 at 04:20:24PM +0200, Markus Elfring wrote:
> > Ifdefs are parsed as comments.
>
> I am curious under which circumstances this software situation
> can be changed for the better support of preprocessor functionality.
It may not support your particular use case, and it is not
> Ifdefs are parsed as comments.
I am curious under which circumstances this software situation
can be changed for the better support of preprocessor functionality.
Regards,
Markus
___
Cocci mailing list
Cocci@systeme.lip6.fr
On Thu, 6 Jun 2019, Markus Elfring wrote:
> > #ifdefs are comments.
>
> I wonder about this wording.
Ifdefs are parsed as comments.
julia
___
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
On Thu, 6 Jun 2019, Markus Elfring wrote:
> > It seems that spatch currently just doesn't understand preprocessor
> > directives at all,
>
> I find this view only partly appropriate.
> There is preprocessor functionality supported by the semantic patch language.
>
> Example:
>
> #ifdefs are comments.
I wonder about this wording.
I hope that the corresponding software situation can be improved further
for complete support of preprocessor functionality.
> If you remove a contiguous sequence of things, the comments between them
> disappear as well.
Such a source code
> It seems that spatch currently just doesn't understand preprocessor
> directives at all,
I find this view only partly appropriate.
There is preprocessor functionality supported by the semantic patch language.
Example:
Hi,
Le 05/06/2019 à 21:56, Julia Lawall a écrit :
On Wed, 5 Jun 2019, Enrico Weigelt, metux IT consult wrote:
Hi folks,
I'd like to hack up some scripts that automatically scan and report
findings on a daily basis, eg. on the linux-next tree. Obviously,
nobody can seriously read this all
