X-Spam-Check-By: sourceware.org content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: bug in cygwin_conv_to_posix_path() caused by period in win32 path Date: Tue, 3 Jul 2007 07:51:04 +0200 Message-ID: From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l635pFDL004767 Dave Korn wrote on Monday, July 02, 2007 7:21 PM: > On 02 July 2007 18:17, Pavel Kudrna wrote: > >> Hi, >> the legal win32 paths containing period like "c:.\" or "c:." are >> incorrectly converted by cygwin_conv_to_posix_path() to "c:./" and >> "c:." respectively. See last two output lines of the attached >> example program. >> Pavel Kudrna > >> c:.\ c:./ >> c:. c:. > > They are legal, but there's no possible way to convert them to > POSIX, which has no notion of a per-drive current directory. Additionally it is no problem to create a directory named "c:." on a non-Windows-kernel-based POSIX system, so those paths are technically correct ;-) - Jörg -- 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/