Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Subject: RE: Re[2]: URL paths in setup.exe Date: Tue, 7 May 2002 21:20:20 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-Has-Attach: content-class: urn:content-classes:message X-MS-TNEF-Correlator: From: "Robert Collins" To: "Pavel Tsekov" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g47BKhg23040 > > How would this confuse them ? I don't think with > file://d|/foo/bar.txt is better thatn file://d/foo/bar.txt. There is a method which converts d:\foo\bar to file URL - isn't it > enough ? There is also a method whic gets the parsed URL as path. > > Btw see the attached program. It is a test for the URL parser. file://d/foo/bar.txt isn't clear whether it's absolute or not. file:///d/foo/bar.txt is on posix, and file://d|/foo/bar.txt is on win32. I know that it doesn't fit in the URI spec, but URI's are universal, and (most) filesystems are local resources only. Rob