public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Tobias Deiminger <tobias.deiminger@posteo.de>
Cc: cocci@inria.fr
Subject: Re: [cocci] Matching a specific declarer?
Date: Mon, 1 Dec 2025 18:21:48 +0100	[thread overview]
Message-ID: <8a6b926e-fee2-42e6-b464-250ef4d55a40@web.de> (raw)
In-Reply-To: <d842430fabc5cfbd805bdf6c8da82ec1@posteo.de>

>>> but actually stumbled upon the issue in a simpler case: I searched for all occurrences of DEVICE_ATTR_RO(attr) in the Linux kernel,
>>
>> Will it become more interesting to clarify your own source code search approaches?
> 
> Sorry, not sure I understand the question. Is there anything I should do, or should avoid to do, or tell about?

It depends …

It seems that an information source like “Coccinellery” can trigger special questions
for more desirable software behaviour.
Further inspirations are generally possible.


> If I manage to compile meaningful results until next week, I maybe add some words about the code search approach to my LPC talk:
> https://lpc.events/event/19/contributions/2198/

I am curious how experience exchange will evolve also by the means of subsequent conferences.


> You mean better Coccinelle documentation?

I still hope that something can be adjusted here.


> I think it's ok. This list is very responsive and helpful, that more than compensates for gaps in documentation, if any.

Thanks for such a positive feedback.


> Also my use case is in the niche of a niche, so really not demanding anything.

But it seems that your development ideas can push existing limits.


>> It might become also interesting with which delay subsequent software
>> tool revisions will be usable.
> 
> Which revisions of which tool do you mean?

Did you notice the announcement “Coccinelle 1.3.1 release” (for example)?
https://lore.kernel.org/cocci/2cd30151-1ac8-4e67-8ecc-962326931d99@inria.fr/
https://sympa.inria.fr/sympa/arc/cocci/2025-11/msg00057.html

Regards,
Markus

      reply	other threads:[~2025-12-01 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 15:28 [cocci] bug: Matching a specific declarer actually matches any declarer Tobias Deiminger
2025-12-01 15:35 ` Julia Lawall
2025-12-01 16:18   ` Tobias Deiminger
2025-12-01 16:00 ` [cocci] Matching a specific declarer? Markus Elfring
2025-12-01 16:53   ` Tobias Deiminger
2025-12-01 17:21     ` 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=8a6b926e-fee2-42e6-b464-250ef4d55a40@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=tobias.deiminger@posteo.de \
    /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