All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] accessing comments
Date: Sun, 26 May 2019 11:27:20 +0200	[thread overview]
Message-ID: <cef0e45d-801b-af84-0958-dfdbadd47e83@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1905260512140.2535@hadrien>

>> Can it be that such a comment would belong to the function call operator
>> (open or closing parenthesis) instead of the identifier “foo”?
>
> You put the comment metavariable on whatever you want.

This functionality is generally nice.


> The report for the comment in the argument list comes from the comment metavariable
> on the complete statement, not on the comment metavariable on foo.

Thanks for such feedback.

It seems that this information can trigger expectations for further clarification
of the desired software behaviour.

Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci

  reply	other threads:[~2019-05-26  9:27 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 19:18 [Cocci] accessing comments Julia Lawall
2019-05-23 12:54 ` Markus Elfring
2019-05-23 13:02   ` Julia Lawall
2019-05-23 14:54     ` Markus Elfring
2019-05-23 15:00       ` Julia Lawall
2019-05-23 15:10         ` Markus Elfring
2019-05-23 19:15         ` [Cocci] Development challenges around OCaml usage for SmPL Markus Elfring
2019-05-24  6:09         ` [Cocci] Checking configuration " Markus Elfring
2019-05-24  6:22           ` Julia Lawall
2019-05-24  6:45             ` Markus Elfring
2019-05-24  6:51               ` Julia Lawall
2019-05-24  6:58                 ` Markus Elfring
2019-05-24  8:15             ` Markus Elfring
2019-05-24  9:55               ` Julia Lawall
2019-05-24 10:43                 ` Markus Elfring
2019-05-24 14:16                 ` Markus Elfring
2019-05-25  6:00             ` [Cocci] Changing include parameters for compilation of OCaml code from SmPL scripts Markus Elfring
2019-05-25 12:10     ` [Cocci] accessing comments Markus Elfring
     [not found]       ` <alpine.DEB.2.21.1905251522470.2799@hadrien>
2019-05-25 13:45         ` Markus Elfring
2019-05-25 23:53           ` Julia Lawall
2019-05-26  7:47             ` Markus Elfring
2019-05-26  7:52               ` Julia Lawall
2019-05-26  8:10                 ` Markus Elfring
     [not found]                   ` <alpine.DEB.2.21.1905260509450.2535@hadrien>
2019-05-26  9:19                     ` Markus Elfring
2019-05-26  8:10                 ` Markus Elfring
2019-05-25 23:54           ` Julia Lawall
2019-05-26  8:00             ` Markus Elfring
     [not found]               ` <alpine.DEB.2.21.1905261004420.2449@hadrien>
2019-05-26  8:21                 ` Markus Elfring
2019-05-27  6:45             ` Markus Elfring
     [not found]       ` <0782D580-3DD6-4419-B5E1-C04215FB2E3B@lip6.fr>
2019-05-25 13:00         ` Markus Elfring
     [not found]           ` <4FE72A81-9D85-4786-898C-A84E2AC5B520@lip6.fr>
2019-05-25 13:35             ` Markus Elfring
2019-05-25 13:41               ` Julia Lawall
2019-05-25 13:56                 ` Markus Elfring
2019-05-25 15:20             ` Markus Elfring
2019-05-26  9:13               ` Julia Lawall
2019-05-26  9:27                 ` Markus Elfring [this message]
2019-05-26 13:05         ` Markus Elfring
     [not found]           ` <eaae9aa05a338fd694057897d830181d@lip6.fr>
2019-05-26 13:33             ` Markus Elfring
     [not found]               ` <eed4a908bc3de6baffcca94ffb42b270@lip6.fr>
2019-05-26 14:33                 ` Markus Elfring
2019-05-26 16:18                 ` Markus Elfring
2019-06-03 16:18     ` [Cocci] Setting the match result by SmPL script rule Markus Elfring
2019-06-02 12:00 ` [Cocci] accessing comments 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=cef0e45d-801b-af84-0958-dfdbadd47e83@web.de \
    --to=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 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.