From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: cocci@inria.fr
Subject: Re: [cocci] Restricting information search for header files
Date: Sun, 9 Nov 2025 15:32:31 +0100 [thread overview]
Message-ID: <4a879286-3488-461b-b41f-c80d82941241@web.de> (raw)
In-Reply-To: <5C6B7613-D38D-463D-A586-4AD8070BD390@inria.fr>
> If you don’t use include headers they will not be included in the file list, only included from other files.
Thanks for another bit of information.
A file filter is already applied then.
Would it be more efficient to exclude undesirable (or unsupported) input files
also by corresponding system configuration parameters?
How many additional data processing resources would be needed for the evaluation
of a final function call like “cocci.exit()” by an SmPL rule script?
Regards,
Markus
prev parent reply other threads:[~2025-11-09 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 12:08 [cocci] Restricting information search for header files Markus Elfring
2025-11-09 12:10 ` Julia Lawall
2025-11-09 12:51 ` Markus Elfring
2025-11-09 14:00 ` Julia Lawall
2025-11-09 14:32 ` Markus Elfring [this message]
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=4a879286-3488-461b-b41f-c80d82941241@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.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 read-only IMAP folder(s) and NNTP newsgroup(s).