Re: LYNX-DEV Lynx version 2.7 compilation problem (SCO Unix)

[T.E.Dickey]

> "T.E.Dickey" <address@hidden> wrote:
> >>    It the meantime, nothing will work short of finding all
> >> the remove() calls in the LYFoo and libwww modules, and replacing
> >> them with unlink().   No macros, as Wayne suggested to you, will
> >> work, because the problem lies in the ultimate translation to
> >> invoke unlink() on Unix.
> >> 
> >>    What I did when the problem was common was to use:
> >> 
> >> #ifdef SCO
> >>    ... unlink(...) ...
> >> #else
> >>    ... remove(...) ...
> >> #endif /* SCO */
> >it's in my configure script (I'd thought that was for VMS, which has
> >no unlink(), but it should work for *NIX systems as well.
> 
>       The objective, at least during the years when I was coordinating
> Lynx development, has been to use platform-independent, portable C code
> as consistently as possible.  remove() was long ago designated as the
> portable function name, so Lynx uses that instead of the Unix unlink()
> or VMS delete().   Similarly, Lynx uses strchr() instead of index(),
> memcpy() instead of bcopy(), memset() instead of bzero(), etc., etc.
> 
>       That's why, aside from memory requirements, and the TCPIP and file
> system issues, it in theory should be able to compile and actually work on
> non-Unix PC systems.
you'd save some time if you actually read my proposed change.  The configure
script checks if 'remove' is found in the library, and if not, #define's
it to 'unlink'.

-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;