From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Julia Lawall <julia.lawall@lip6.fr>,
Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] How to replace obsolete #ifdef's?
Date: Fri, 7 Jun 2019 14:01:48 +0200 [thread overview]
Message-ID: <a2d09fdf-456d-e6ae-1dae-b24b9f683d57@metux.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1906061233360.21477@hadrien>
On 06.06.19 12:34, Julia Lawall wrote:
>
>
> On Thu, 6 Jun 2019, Markus Elfring wrote:
>
>>> #ifdefs are comments.
>>
>> I wonder about this wording.
>
> Ifdefs are parsed as comments.
Any chance that it gets extended to understand at least such rather
simple cases ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-06-07 12:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 16:25 [Cocci] how to replace obsolete #ifdef's Enrico Weigelt, metux IT consult
2019-06-05 19:51 ` [Cocci] How to replace obsolete #ifdef's? Markus Elfring
2019-06-05 20:52 ` [Cocci] how to replace obsolete #ifdef's Julia Lawall
2019-06-05 21:42 ` Enrico Weigelt, metux IT consult
2019-06-06 5:46 ` Julia Lawall
2019-06-06 9:30 ` [Cocci] How to replace obsolete #ifdef's? Markus Elfring
2019-06-06 10:34 ` Julia Lawall
2019-06-06 14:20 ` Markus Elfring
2019-06-06 15:34 ` David Young
2019-06-07 12:01 ` Enrico Weigelt, metux IT consult [this message]
2019-06-07 12:30 ` Julia Lawall
2019-06-06 9:15 ` Markus Elfring
2019-06-06 9:39 ` Julia Lawall
2019-06-07 12:05 ` Enrico Weigelt, metux IT consult
2019-06-07 12:32 ` Julia Lawall
2019-06-07 13:40 ` Markus Elfring
2019-06-07 16:33 ` Julia Lawall
2019-06-07 17:26 ` Markus Elfring
2019-06-07 17:36 ` Markus Elfring
2019-06-07 18:48 ` Markus Elfring
2019-06-07 18:59 ` Julia Lawall
2019-06-08 7:49 ` [Cocci] Handling of designated initialisers by SmPL? Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a2d09fdf-456d-e6ae-1dae-b24b9f683d57@metux.net \
--to=lkml@metux.net \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).