Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <20030604022225.82119.qmail@web40609.mail.yahoo.com> Date: Tue, 3 Jun 2003 19:22:25 -0700 (PDT) From: Greg Fenton Subject: Re: Path separator To: cygwin AT cygwin DOT com In-Reply-To: <3EDD5587.8060004@cygwin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Larry Hall wrote: > > Max is right (surprised Max? ;-) ) But I want to point out something > else about what you've said. If your main concern is paths, don't > convert '/' to '\'. Windows understands both under the hood. > (Cygwin > does too but that's another matter). However, this is the least of > your problems as Max clearly states. > Yes, Max is right. I hadn't thought about the difference between a "native win32" environment vs. "from a DOS prompt on a system that has Cygwin in its path" (I rarely, if ever, run in a "native win32" environment...) I don't understand why we don't just get MSFT to ship cygwin1.dll... :-) One last point: not all flavours of Windows that are targetted for SWISH-E support the "/" vs. "\" (e.g. Win95/98). At least, I don't think they support it...but again, its been a long while since I've sat in front of such a box. Thanks for the info! greg_fenton. ===== Greg Fenton greg_fenton AT yahoo DOT com __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/