Re: lynx-dev overuse of system-specific conditionals (was: cygwinpatch

[vtailor]

>     * From: Doug Kaufman <address@hidden>
>     * Date: Mon, 1 May 2000 20:41:42 -0700 (PDT)
>   
>On Mon, 1 May 2000, Klaus Weide wrote:
>
>> But these choices shouldn't be hardwired into the source code in such
>> a way that it gets near-impossible to disentagle them, for someone who
>> looks at the source code (and perhaps doesn't even know what DJGPP or
>> CYGWIN is).
>> ...
>> I mean, "don't use cp in a cygwin environment" is a preference, a choice
>> you made, not something that is required to run in a cygwin environment.
>> You think it's more appropriate as a default, and I have no problem with
>> that (but some questions, see below).
>
>Point taken.
>
>> > Indeed, the SH_EX changes are Senshu Hiroyuki's preferences, which
>> > have not yet been accepted for general use.
>>
>> As well as WIN_EX?
>
>I thought that the difference between SH_EX and WIN_EX was that the
>latter was thought to be generally acceptable code for use in Windows
>platforms. I must admit that I wasn't paying that much attention,
>since I wasn't using cygwin at the time this was discussed. I am
>not sure who accepted the WIN_EX code. Was it Hiroyuki who made the
>original decisions? I, at least, was hampered by the documentation in
>Japanese, and have trouble reading through the code to decide what it
>does and why.
>
>> Anyway, I'd say don't be afraid to add a new preprocessor symbol
>> where it makes sense.  They don't all need to be exposed in userdefs.h
>> or in the makefile(s).  For example, for the "use cp or not" question,
>> something like
>> ...
>> would be better than the current situation.  That #define could be just
>
>> > Since most Windows users wouldn't have cp, this saves the need to
>> > distribute a compatible cp with the lynx binary.
>>
Look, you clowns, the whole idea of Cygwin was that you could use the
./configure script, just like any other Unix.  And that, to programs
running under cygwin.dll, the Dos/Windows file systems look exactly
like Unix, rm, cp, and all.  That means there should be _no_ need at
all for specific Cygwin defines.

Actually, if someone would please do a native Windows implementation of
ash.exe or bash.exe, it would be possible to run ./configure directly
under Windows for MingW32, and by extension, all the vanilla Windows
compilers.

be little or no need 


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