Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/3/85; site ukma.UUCP
Path: utzoo!watmath!clyde!cbosgd!ukma!david
From: david@ukma.UUCP (David Herron, NPR Lover)
Newsgroups: net.lang.c
Subject: Re: if(p)
Message-ID: <2245@ukma.UUCP>
Date: Fri, 27-Sep-85 09:42:50 EDT
Article-I.D.: ukma.2245
Posted: Fri Sep 27 09:42:50 1985
Date-Received: Sun, 29-Sep-85 06:54:46 EDT
References: <1671@brl-tgr.ARPA> <516@talcott.UUCP>
Reply-To: david@ukma.UUCP (David Herron, NPR Lover)
Organization: Univ. of KY Mathematical Sciences
Lines: 17

In article <516@talcott.UUCP> tmb@talcott.UUCP (Thomas M. Breuel) quotes:
>In article <1671@brl-tgr.ARPA>, ART@ACC.ARPA (Art Berggreen) writes:
>> From an abstract language viewpoint, an "if" statement conditionally
>> executes a block of statements based on whether the control statement
>> evaluates to a condition of *TRUE*.  Pointers by themself do not
>> have attributes of TRUE vs FALSE.  Thus, "if(pointer)" makes less semantic

I disagree...  Pointers have VALID and INVALID values.  So when you
say if(p) you're asking if it has a VALID or INVALID value.  It's
just that conveniently most machines have 0 as the INVALID value.
-- 
--- David Herron
--- ARPA-> ukma!david@ANL-MCS.ARPA
--- UUCP-> {ucbvax,unmvax,boulder,oddjob}!anlams!ukma!david
---        {ihnp4,decvax,ucbvax}!cbosgd!ukma!david

Hackin's in me blood.  My mother was known as Miss Hacker before she married!