lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Foteos Macrides
Subject: Re: LYNX-DEV Re: DOS, DOS and Windows
Date: Fri, 25 Oct 1996 11:09:40 -0500 (EST)

Doug Lawson <address@hidden> wrote:
>On Fri, 25 Oct 1996, Wayne Buttles wrote:
>
>> On Fri, 25 Oct 1996, Doug Lawson wrote:
>> > 
>> > > 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.  
>> > 
>> > It's been a while since I used Borland 3.anything but I don't remember 
>> > having that problem...............
>> 
>> Umm, maybe it is a case of me not quite understanding the real problem. 
>> Here is a sample from HTTP.c (in HTML_FORM): 
>> 
>> source = HTAnchor_findChildAndLink(me->node_anchor, 0, action, 0); 
>> 
>> Needed to be:
>> 
>> source = HTAnchor_findChildAndLink(me->node_anchor, NULL, action, NULL); 
>
>Well, that would indicate that the compiler is not compliant.  Obviously 
>NULL is #defined to something other than 0.  Like I said, it's been some 
>time since I used BC3.x .

        NULL should be defined in the compiler's headers (stdio.h) as
0 with a void pointer type cast:

        #define NULL ((void *) 0)

        How does Borland C define it?

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;



reply via email to

[Prev in Thread] Current Thread [Next in Thread]