[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #36677] canonicalize_file_name: inconsistent b
[Octave-bug-tracker] [bug #36677] canonicalize_file_name: inconsistent behavior for non-existing files
Thu, 30 Aug 2012 23:25:21 +0000
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0
Follow-up Comment #8, bug #36677 (project octave):
canonicalize_file_name() is never going to be the right function for this
situation. It isn't particularly broken, it is just defined a particular way
by GNU for their version of libc. Lots of people rely on the current behavior
so there isn't much hope of changing it.
make_absolute_pathname() isn't a GNU or gnulib function but an Octave one.
Therefore, we could potentially modify it to do whatever we want. The
function is pretty short. If you are familiar with C++ you should take a
look. The file is liboctave/oct-env.cc. The function is make_absolute() at
line 326. I see that there is already a FIXME comment that the behavior may
not be correct on all systems. Duh! It seems like this must have been coded
in a bit of a hurry.
Reply to this item at:
Message sent via/by Savannah