Re: LYNX-DEV Re: DOS, DOS and Windows

[Doug Lawson]

> One thing I missed about compiling Lynx code (actually most Un*x code) 
> with Borland C 3.1 (not sure about other versions) is 0 != NULL.  This has
> bitten me many times and I always forget *sigh*

It's been a while since I used Borland 3.anything but I don't remember 
having that problem.  Are you saying 
        - there is no #define NULL 0
        - the base of the heap (NULL pointer) does not resolve to 0 ?
          or
        - the compiler doesn't treat 
                if(ptr == NULL) 
          the same way as 
                if(ptr)
          ??????

Only the third case should present a serious problem, and I don't 
remember BC 3.1 having that problem.....  Even though the base of the
heap may not have a numerical address of 0, I remember the compiler being 
compliant and treating it as if it were 0, which is all the ANSI C specs 
call for.

Maybe I've forgotten. 

Doug Lawson


;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;