|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #44682] Fullfile does not support network share addresses on windows platofrm |
Date: | Wed, 01 Apr 2015 17:32:45 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33 |
Update of bug #44682 (project octave): Status: None => Confirmed Operating System: Microsoft Windows => Any _______________________________________________________ Follow-up Comment #5: I'd swear I've seen or maybe even fixed a similar bug a while ago..... Yes: http://hg.savannah.gnu.org/hgweb/octave/rev/c304687571c8 OK I'll have a look later on, if nobody beats me to it. This one is different as it also fails on *nix; it looks nastier as there's no reliable way to distinguish an erroneous path ('\\wrong\path\name') from a valid network path ('\\server\d\rive\path'). fullfile.m simply strips multiple leading fileseps away. Maybe just assuming that two consecutive fileseps always constitute a network path would do the trick? (with a check on Windows that there's no <driveletter><colon> sequence> ?) In addition fullfile.m doesn't know about e.g., file:///rootdir/path ftp://server/rootdir/path www://server/rootdir/path http://server/rootdir/path ...and other path forms. But that's a separate issue. OS -> Any; Status -> confirmed _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?44682> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |