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: <3E18D5A7.3050707@hack.kampbjorn.com> Date: Mon, 06 Jan 2003 02:02:31 +0100 From: Hack Kampbjorn User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en,da,es,ca MIME-Version: 1.0 To: LA Walsh CC: cygwin AT cygwin DOT com Subject: Re: Repost, different list...File::Spec, Cygwin, Syntactic vs. Semantic path analysis References: <012901c2b496$3f4955e0$1403a8c0 AT sc DOT tlinx DOT org> In-Reply-To: <012901c2b496$3f4955e0$1403a8c0@sc.tlinx.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit LA Walsh wrote: > Cygwin, and possibly, the Win32 module, are inconsistent in handling > the differences between i:/foobar/ and i:. On one hand i: is > considered a 'volume' but on the other hand i:/ seems to evaluate to > the same, incorrect, value. In "Win32", each 'fs' of form ":', x > of class <[:alpha:]>, there is a process-specific "current > directory". This can be seen by: > In the old DOS days yes, but in Win32 there is only one current directory. The illusion of having a current directory per drive and an active drive is maintained in cmd.exe (or is it in the MS C runtime?). As cygwin doesn't use it, i:foobar and i:/foobar is always the same. -- Med venlig hilsen / Kind regards Hack Kampbjørn -- 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/