[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #45816] canonicalize_file_name() changed behav
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #45816] canonicalize_file_name() changed behavior between 3.8.2 and 4.0.0 on windows |
Date: |
Mon, 31 Aug 2015 16:10:54 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Firefox/38.0 |
Follow-up Comment #4, bug #45816 (project octave):
Based on the response from upstream, it seems to me we should probably leave
canonicalize_file_name alone. I would advocate for keeping the Octave function
a thin wrapper around the C function, as we do for other functions.
If users want a function to return a canonical absolute path that *also*
respects the native filesep conventions, that should probably be
make_absolute_filename or some other not-yet-written post-processing wrapper
around canonicalize_file_name.
And of course document the differences and why we have 2 or 3 different
functions to construct an absolute path name :)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45816>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/