At 10:07 AM 5/6/2002, Christopher Murray wrote: >As it currently stands, canonpath will not strip out multiple occurrences of // in >file paths when the script is executed from >within a cygwin shell. The relevant line from /usr/lib/perl5/5.6.1/File/Spec/Unix.pm >that strips out multiple /'s is > >$path =~ s|/+|/|g unless ($^O eq 'cygwin'); > >I assume this regexp substitution is ignored for cygwin because we would not want to >munge instances where // refers >to a network share (something regular unix doesn't need to worry about), but is it >wise to also ignore all multiple forward >slashes when they occur in the middle of a path? Or is this simply a non-issue >because, for the most part, it seems like >most (if not all?) programs don't really seem to care about multiple path separators?
Right. A sequence of multiple path separators is condensed into 1 for all but the first. There the convention is to do something that is application specific. >For what it's worth, canonpath in ExtUtils::MM_Unix (and MM_Cygwin), uses > >$path =~ s|(?<=[^/])/+|/|g; > >which seems to do what I expect (leaves // at the front of a path alone, but replaces >all remaining // with /). The only weakness I see with this is that it will not >replace ///shareName/path with //shareName/path, but that is a minor matter, at least >as it concerns me. Sorry, can't help here. Reading complex regular expressions hurts my head! ;-) Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- 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/
