From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Kees Cook <keescook@chromium.org>, cocci@inria.fr
Subject: Re: [cocci] how to check a for "don't care" state of a variable?
Date: Sun, 9 Oct 2022 20:16:35 -0600 [thread overview]
Message-ID: <Y0OAg/Sa8pfNDy33@zx2c4.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2210092018320.21609@hadrien>
On Sun, Oct 09, 2022 at 08:19:36PM +0200, Julia Lawall wrote:
>
>
> On Sun, 9 Oct 2022, Kees Cook wrote:
>
> > On Sun, Oct 09, 2022 at 08:02:24PM +0200, Julia Lawall wrote:
> > > Thanks. I have added a link from the documentation page.
> >
> > Thanks!
> >
> > > > And I've sent a PR for some missing docs in Coccinelle itself:
> > > >
> > > > https://github.com/coccinelle/coccinelle/pull/290
> > >
> > > Could you send it by email please?
> >
> > Done now.
>
> Thanks
>
> > Is there a good place for finding this python documentation? I
> > didn't see anything that really showed how to use it, and have mostly
> > gone off of existing examples.
>
> I'm not really an expert on what is supported in python. Someone once
> suggested that reflection could be used to find out what functions are
> available. Normally, they are the same as are supported for OCaml.
The important one I found was `cocci.include_match(False)`.
Jason
next prev parent reply other threads:[~2022-10-10 5:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 23:11 [cocci] how to check a for "don't care" state of a variable? Kees Cook
2022-10-08 3:09 ` Kees Cook
2022-10-08 7:43 ` Julia Lawall
2022-10-08 8:55 ` Markus Elfring
2022-10-08 9:00 ` Julia Lawall
2022-10-08 9:15 ` Markus Elfring
2022-10-08 11:02 ` Markus Elfring
2022-10-09 15:10 ` Kees Cook
2022-10-09 15:12 ` Julia Lawall
2022-10-09 15:56 ` Markus Elfring
2022-10-09 17:37 ` Kees Cook
2022-10-09 18:02 ` Julia Lawall
2022-10-09 18:16 ` Kees Cook
2022-10-09 18:19 ` Julia Lawall
2022-10-10 2:16 ` Jason A. Donenfeld [this message]
2022-10-10 19:12 ` [cocci] Reconsidering selected SmPL code 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=Y0OAg/Sa8pfNDy33@zx2c4.com \
--to=jason@zx2c4.com \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=keescook@chromium.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.