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 From: "linda w \(cyg\)" To: Subject: Perl package File::Spec confused under cygwin Date: Fri, 20 Dec 2002 13:27:50 -0800 Message-ID: <001b01c2a86e$a5da95f0$1403a8c0@sc.tlinx.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal File::Spec is supposed to provide a OS independent way of parsing and creating pathnames. For example, a 'splitpath' can product a volume $dir and $file. I'm not sure what constitutes a volume but I'd think C: D: would count as separate. Under cygwin, it only handles/parses unix pathnames but not native windows pathnames 'c:\windows\filename' will yield a vol='', dir='' and filename='d:\windows\filelname' -- not what one would expect. Using forward slashes yields: vdf='', 'd:/windows/,'filename'. Further use to break down the directory path into components would yield D: as a first directory and 'windows' as a 2nd level dir. Note that the forward slash has now disappeared indicating what I believe to be improper symantics as d:windows != D:\windows unless d:'s curdir is = to the root dir. Guess when the module detects the OS type, it needs to have a separate type for the cygwin environment. -linda -- 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/