Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site talcott.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!talcott!tmb From: tmb@talcott.UUCP (Thomas M. Breuel) Newsgroups: net.lang.c Subject: RE: if(p) Message-ID: <516@talcott.UUCP> Date: Tue, 24-Sep-85 13:30:21 EDT Article-I.D.: talcott.516 Posted: Tue Sep 24 13:30:21 1985 Date-Received: Sat, 28-Sep-85 06:47:07 EDT References: <1671@brl-tgr.ARPA> Organization: Harvard University Lines: 13 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 Where do you take that bit of wisdom from? Obviously, 'C' works differently, from an abstract and practical point of view. If you like abstractions, why don't you consider 'if' a message that is sent to the object following it in parentheses and that then decides to execute the statement following it :-). Thomas.