All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Usage of "expressions" and "identifiers" with SmPL
Date: Sat, 8 Oct 2016 11:25:52 +0200	[thread overview]
Message-ID: <3bbf1a67-5fae-7d34-d39c-b3820082441d@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1610081029050.7750@hadrien>

>> Which details from my description approach are inappropriate in your view?
> 
> The whole numbered list was pointless.

I hope that we can eventually benefit from such a disagreement
in constructive ways.


> He was trying to understand what is meant by "idexpression".

Yes. - The functionality and relationship of this key word was unclear
to some degree together with the usage of "identifiers", wasn't it?


> This is a concept particular to Coccinelle,

I can follow this view.


> that was introduced because we discovered that sometimes one wants to
> focus only on identifiers, but to also specify their types.

Thanks for this kind of background information.


> I couldn't tell from your answer what question it was intended to be relevant to,

I am curious if a bit more clarification of the relevance and my
corresponding intention would be needed.


> but I don't think it is the same as the one he was asking.
> It seems to be a generic overview of what Coccinelle does.

I am also unsure if and how quick Nikolaus Rath will find the provided
technical details a bit useful.


> Someone who has to read so much text and in the end has no information
> about the question he was asking will not likely get a good impression
> about the software he is trying to use.

A beginner should usually read some text for the desired learning experience.
Can it be that you worry a bit too much about the potential for
bad impressions around your software?

Would you like to start another marketing project?


I find that this mailing list gets only low message traffic so far.
So I would imagine that most well-intended discussion contributions could
be useful. Is the mixture of presented topics reasonable?


We came along different views around the usage of "expressions"
in previous discussions, didn't we?
You repeated the explanation "An expression is something that has a value."
which is reasonable to some degree. I would like to know then:
Which "value" is provided by the software construct "idexpression"
in the semantic patch language?

Regards,
Markus

  reply	other threads:[~2016-10-08  9:25 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  3:27 [Cocci] Replacing one (specific!) type with another Nikolaus Rath
2016-10-05  5:45 ` Julia Lawall
2016-10-05 16:09   ` Nikolaus Rath
2016-10-05 16:39     ` Michael Stefaniuc
2016-10-05 17:21     ` [Cocci] Replacing one variable name " SF Markus Elfring
2016-10-05 22:34       ` Nikolaus Rath
2016-10-06  5:42         ` SF Markus Elfring
2016-10-06  5:56         ` Julia Lawall
2016-10-05 20:02     ` [Cocci] Replacing one (specific!) type " Julia Lawall
2016-10-05 22:38       ` Nikolaus Rath
2016-10-06  5:55         ` Julia Lawall
2016-10-08  3:16           ` Nikolaus Rath
2016-10-08  5:50             ` Julia Lawall
2016-10-08 20:45               ` Nikolaus Rath
2016-10-08 21:23                 ` Julia Lawall
2016-10-09  6:32                 ` SF Markus Elfring
2016-10-08  6:48             ` [Cocci] Usage of "expressions" and "identifiers" with SmPL SF Markus Elfring
2016-10-08  6:57               ` Julia Lawall
     [not found]               ` <alpine.DEB.2.10.1610080850470.7750@hadrien>
2016-10-08  7:49                 ` SF Markus Elfring
2016-10-08  7:56                   ` Julia Lawall
2016-10-08  8:26                     ` SF Markus Elfring
2016-10-08  8:38                       ` Julia Lawall
2016-10-08  9:25                         ` SF Markus Elfring [this message]
2016-10-08 20:28                           ` Nikolaus Rath
2016-10-09  7:49                             ` SF Markus Elfring
2016-10-09 20:38                               ` Nikolaus Rath
2016-10-10  6:48                                 ` SF Markus Elfring
2016-10-10  6:50                                   ` Julia Lawall
2016-10-06  6:30         ` [Cocci] Replacing one (specific!) type with another SF Markus Elfring
2016-10-08  4:22       ` Nikolaus Rath
2016-10-08  5:31         ` Julia Lawall
2016-10-08 20:52           ` Nikolaus Rath
2016-10-08 21:21             ` Julia Lawall
2016-10-09 20:45               ` Nikolaus Rath
2016-10-10  4:49                 ` Julia Lawall
2016-10-10  4:54                 ` Julia Lawall
2016-10-10 15:56                   ` Nikolaus Rath
2016-10-10 18:45                     ` Nikolaus Rath
2016-10-10 19:45                       ` Julia Lawall
2016-10-10 21:27                         ` Nikolaus Rath
2016-10-10 21:33                           ` Julia Lawall
2016-10-10 23:00                             ` Nikolaus Rath
2016-10-11  6:51                               ` Julia Lawall
2016-10-12 15:08                                 ` Nikolaus Rath
2016-10-12 20:37                                   ` Julia Lawall
2016-10-05  5:51 ` SF 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=3bbf1a67-5fae-7d34-d39c-b3820082441d@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=cocci@systeme.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.