From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: cocci <cocci@systeme.lip6.fr>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Cocci] spatch for trivial pointer comparison style?
Date: Sat, 15 Nov 2014 07:11:20 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1411150708500.2049@localhost6.localdomain6> (raw)
In-Reply-To: <1415982122.5912.14.camel@perches.com>
On Fri, 14 Nov 2014, Joe Perches wrote:
> On Fri, 2014-11-14 at 10:18 +0100, Julia Lawall wrote:
> > On Thu, 13 Nov 2014, Joe Perches wrote:
> []
> > > Yes, I agree with some of the things Al Viro said
> > > there, but isn't 'type t; t *p;' a subset of
> > > "expression *e"?
>
> > No. How would you expect it to be different.
>
> []
No. [] and * are treated completely differently.
> > type t means that the type
> > is known. expression *e means that there is a * in the type.
>
> I had thought "expression *" could be r-value and
> "type t; t *p;" could be l-value.
No, you made that one up :) As we considered that it would be common to
want to specify the type of an expression, we thought it would be tiresome
to have to put eg expression int x. So you can just say int x.
The downside is that people write
identifer x;
and then don't understand the error message, because any misspelled
metavariable kind is considered to be a type name.
julia
> But then I don't find (or maybe don't parse too well)
> the coccinelle documentation that specifies these
> type relationships.
>
> cheers, Joe
>
>
>
next prev parent reply other threads:[~2014-11-15 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 19:55 Joe Perches
2014-11-14 6:06 ` [Cocci] " Julia Lawall
2014-11-14 6:12 ` Joe Perches
2014-11-14 9:18 ` Julia Lawall
2014-11-14 16:22 ` Joe Perches
2014-11-15 6:11 ` Julia Lawall [this message]
2014-11-14 10:08 ` SF Markus Elfring
2014-11-14 10:31 ` Julia Lawall
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=alpine.DEB.2.02.1411150708500.2049@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®