Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 16 Jul 2004 15:01:28 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: UNC Pathname Handling within Applications Message-ID: <20040716130128.GW1389@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20040715033232.GP25893@eumel.yoo.local> <20040715233034.GA3729@eumel.yoo.local> <6.1.0.6.0.20040715221848.033c3b40@pop.prospeed.net> <20040716120644.GB745@eumel.yoo.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040716120644.GB745@eumel.yoo.local> User-Agent: Mutt/1.4.2i On Jul 16 14:06, Thorsten Haude wrote: > I think some people might see the surprising path, *think* the > software is broken and stop using it. Another problem ist the toolkit. > > I agree that the leading extra slash should be supported, but it might > not be as easy as it sounds. Thorsten, even if I repeat other postings, please note that double slashes are absolutely fine according to the standards. Leading double slashes may have a special meaning on POSIX implementations and the *well* *known* Windows specific meaning is an UNC path for accessing network (CIFS) shares. Honestly, there should be no surprise in that fact to users of your software. If you really want to mangle file names in your application instead of just leaving them alone, then your application should honor that fact, to be *portable*. This isn't us being mean, as usual, that's just fact. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/