[Octave-bug-tracker] [bug #45816] canonicalize_file_name() changed behavior between 3.8.2 and 4.0.0 on windows

[Philip Nienhuis]

Follow-up Comment #12, bug #45816 (project octave):

@Rik comment #7
Based on e.g., bug #43979, it is Octave itself that got "peeved" on
canonicalize_file_name's output, isn't it.

The problem is outlined in my post in the maintainers ML:
On Windows, Octave gets paths with backslash fileseps returned from e.g. "pwd"
or "fullfile" commands that -once combined with canonicalize_file_name's
output- induce problems when fed to yet other regular Octave functions that
rely on consistent fileseps. 
IOW, functions returning / or \ fileseps at will are unacceptable for several
other often used Octave functions.

Too bad that there seem to be no filesep consistency tests in place for
make_absolute_filename and canonicalize_file_name - if there were this would
have been catched immediately at the time. If you want I'll try to come up
with something.

BTW I suppose this is a real regression. Shall I mark it as such?

    _______________________________________________________

Reply to this item at:

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

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