Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 28 Sep 2000 10:49:58 -0400 From: Jeffrey Juliano Reply-To: Jeffrey Juliano To: cygwin AT sources DOT redhat DOT com Subject: Re: gmake is slow under cygwin Message-ID: <3770557360.970138198@dsl-64-34-95-237.telocity.com> In-Reply-To: <20000927002710.A7341@cygnus.com> X-Mailer: Mulberry/2.0.5b2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, Sep 27, 2000 at 12:27 AM -0400, Chris Faylor wrote: > On Tue, Sep 26, 2000 at 11:55:27PM -0400, Jeffrey Juliano wrote: >> My proposed change would make path handling even less symmetric, so >> perhaps it's not a good idea afterall. Is this even worth discussing? > > No, I don't think so. I'm not really going to be swayed on this issue. Agreed. Especially after finding the thread "File name syntax (WAS: RE: FW: Can not config sshd)", which I had not previously read. Sorry to bring it up again. In that thread, Chris points out that a leading double-slash is allowed to be handled as a special case, and there are unix systems that do so. I guess that means that any code that doesn't take this into account is broken anyway a portability standpoint. -jeff -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com