[Octave-bug-tracker] [bug #44682] Fullfile does not support network share addresses

[Philip Nienhuis]

Follow-up Comment #13, bug #44682 (project octave):

Rik
@comment #11:
IMO responsibility for valid paths in case of ('/', '/abc')-constructs should
be the responsibility of the user, not of fullfile.m; after all the *form* of
the proposed fullfile.m result represents valid path name (UNC) *syntax* on
Windows.
I foresee that such constructs could be cooked up by scripts, so your question
is quite right.


@comment #12:
What usually happens is that on at least Windows network paths, drive letters
(and partial paths from there like "f:\path\to\shared\folder") are replaced by
share names that appear right after the server name:
\\server\sharename\path\to\subdir\relative\to\network\share

\\serverc:\tmp\dir1\dir2 is syntax I've never seen on Windows.
I'm familiar with the other two \\?\ UNC forms, but they're rarely if ever
used by ordinary users, I've only used them when poking around in the mountmgr
section of the Windows registry.

And then we have the URL forms I mentioned in a previous post:

file:///some/path
ftp://server/path
etc


I think those \\?\ and file:/// and URL path forms had better be left for a
future fullfile.m upgrade, as soon as Matlab supports it as well.


Right now the relevant thing is whether //server/share/file is valid on Linux
(e.g., samba etc when referring to shares on Windows hosts).
If not, the suggestion by the OP will work fine and is the simplest; yet I do
not like adding integers and logicals (1 + ispc()).
BTW the OP's mod would also morph ('\', \ abc') into '\\abc'.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44682>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/