Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <000901c1d474$50d3fed0$0610a8c0@wyw>
From: "Wu Yongwei" <adah AT netstd DOT com>
To: "Randall R Schulz" <rrschulz AT cris DOT com>
Cc: <cygwin AT cygwin DOT com>
Subject: Re: cygwin1.dll bug in ftime
Date: Tue, 26 Mar 2002 11:12:41 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300

When I write new code, _I_ will not use ftime again. In fact, I have fixed
my synctime program with an ugly "ifndef __CYGWIN__" macro and replaced
code using ftime with _timezone (timezone). However, breaking legacy code
is not good behaviour for a (runtime) environment.

Also, I don't intend my code will run on any platforms. In fact, seldom
will any code with a little complexity without real-environment test. I DO
want my code to run flawlessly on frequently-used x86 Unix enviroments,
Linux, FreeBSD, Cygwin, etc.

Sorry that I do not understand your English very well. But I hope I have
expressed my meanings.

Best regards,

Wu Yongwei

--- Original Message from Randall R Schulz ---

Yongwei,

At 18:45 2002-03-25, you wrote:
>...
>
>Hope I am clear enough. I am arguing here for a BETTER Cygwin.

No. You're asking to be let off the hook for either writing intrinsically
portable code or of featuring it with conditional compilation directives
so that it functions as you want it to on all platforms you want to claim to
support.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/