[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1411150708500.2049@localhost6.localdomain6>
Date: Sat, 15 Nov 2014 07:11:20 +0100 (CET)
From: Julia Lawall <julia.lawall@...6.fr>
To: Joe Perches <joe@...ches.com>
cc: cocci <cocci@...teme.lip6.fr>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Cocci] spatch for trivial pointer comparison style?
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
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists