[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev overuse of system-specific conditionals (was: cygwin patc
From: |
Henry Nelson |
Subject: |
Re: lynx-dev overuse of system-specific conditionals (was: cygwin patc |
Date: |
Sat, 6 May 2000 13:17:52 +0900 (JST) |
> Some of the WIN_EX stuff is really cute and totally unavailable under
> Unix. Maybe my endorsement of it will hasten its removal.
Not sure what you want to say, but personally I rather like "really cute
and totally unavailable under Unix."
I admit that _in retrospect_ it seems that the three defines really should
have been all within SH_EX as the changes were preferences of a handful of
people represented by one programmer. I think there was a general feeling
at the time the patch was incorporated, however, that the changes would be
quite beneficial overall. Looking back through CHANGES I can see Leonid
and others worked pretty hard to make the added features fully functional
without affecting other ports.
The code under all three of those *_EX defines needs to be revisited and
either brought out from under them or discarded as appropriate. It seems
the CJK_EX stuff is nearly obsolete? (At least I'm not aware of anything
possibly under CJK_EX except the manual override routines.) Now's the time
since a new development round has just started.
__Henry
;
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
;