[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070815094356.GA18253@aurum.uhlenkott.net>
Date: Wed, 15 Aug 2007 02:43:56 -0700
From: Jason Uhlenkott <jasonuhl@...onuhl.org>
To: Jan Engelhardt <jengelh@...putergmbh.de>
Cc: Rene Herman <rene.herman@...il.com>,
Arjan van de Ven <arjan@...radead.org>,
Tim Bird <tim.bird@...sony.com>,
linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: kfree(0) - ok?
On Wed, Aug 15, 2007 at 11:20:33 +0200, Jan Engelhardt wrote:
>
> On Aug 15 2007 10:37, Rene Herman wrote:
> > On 08/15/2007 09:28 AM, Jan Engelhardt wrote:
> >> On Aug 14 2007 16:21, Jason Uhlenkott wrote:
> >
> >> > On Tue, Aug 14, 2007 at 15:55:48 -0700, Arjan van de Ven wrote:
> >> > > NULL is not 0 though.
> >> > It is. Its representation isn't guaranteed to be all-bits-zero,
> >>
> >> C guarantees that.
> >
> > C guarantees what? If you're disagreeing with Jason -- he's right.
>
> http://coding.derkeiler.com/Archive/C_CPP/comp.lang.c/2003-11/1808.html
That's about representation of integers types. Pointer types are
another matter.
C99 sections 6.2.5 and 6.2.6 cover this.
This is all just academic language lawyering, of course. Any machine
on which a pointer isn't NULL after being memset to 0 has serious
quality of implementation issues.
-
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