[Octave-bug-tracker] [bug #52071] reporting functions that shadow a core library function is inconsistent.

[Mike Miller]

Update of bug #52071 (project octave):

                Category:                     GUI => Interpreter            

    _______________________________________________________

Follow-up Comment #1:

I do see a warning when the GUI starts, and also when using addpath in the
GUI. So I don't see any difference between command-line and GUI with regards
to this behavior. The difference only has to do with how the function override
is added to the path.

1. chdir(dir) or cd(dir) → no warning
2. addpath(dir) → warning
3. start Octave in dir → warning
4. start Octave with --path $dir option → no warning

However, if the override is a compiled builtin, for example "exp" instead of
"flip", then a warning *is* issued when the --path option is given. This
probably has to do with the order of path initialization and of initial
scanning of m-files and oct-files in the load path.

    _______________________________________________________

Reply to this item at:

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

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