Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Wed, 14 Jun 2000 23:46:00 -0400 To: Cygwin Subject: Re: Problem compiling perl module Term::ReadKey under cygwin Message-ID: <20000614234600.A14000@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Cygwin References: <3947B531.D14BF8DD@adaptivesilicon.com> <3947BBE9.5B33C61E@ece.gatech.edu> <03ec01bfd678$b2fce140$032c1818@rochester.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <03ec01bfd678$b2fce140$032c1818@rochester.rr.com>; from lincoln2@rochester.rr.com on Wed, Jun 14, 2000 at 11:20:44PM -0400 On Wed, Jun 14, 2000 at 11:20:44PM -0400, Terry Lincoln wrote: >Let's stick to a convention for awhile, please! The current one has my >vote. Thanks. I anticipated that the current behavior would flush out some buggy code. Some of it was actually in some of the tools on sourceware. It's obvious to me that if a UNIX application is using '\' to indicate a path separator, it's just plain broken. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com