From owner-freebsd-chat Thu Aug 10 10:46:24 2000 Delivered-To: freebsd-chat@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 3193C37B53C for ; Thu, 10 Aug 2000 10:46:21 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id MAA86938; Thu, 10 Aug 2000 12:46:17 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Thu, 10 Aug 2000 12:46:17 -0500 (CDT) From: David Scheidt To: Anatoly Vorobey Cc: "Thomas M. Sommers" , chat@freebsd.org Subject: Re: C time functions - problem In-Reply-To: <20000810191221.A12280@happy.checkpoint.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 10 Aug 2000, Anatoly Vorobey wrote: :On Thu, Aug 10, 2000 at 01:30:44AM -0400, Thomas M. Sommers wrote: :> :> "An integer constant expression with the value 0, or such an expression :> cast to type void *, is called a null pointer constant. If a null :> pointer constant is converted to a pointer type, the resulting pointer, :> called a null pointer, is guaranteed to compare unequal to a pointer to :> any object or function." :> :> There are very few circumstances in which you need to cast 0 to make it :> a null pointer constant. : :I am not aware of any such circumstances at all. 0 can always be used :instead of NULL, and, since I find it completely unambiguous, I always :use 0 for null pointers. This is only true on systems where 0 is not a valid address. On such systems, NULL pointers aren't equal to 0. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message