[Octave-bug-tracker] [bug #56881] Command line functions are visible from m files

[Rik]

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

I think the end state--capricious code that executes variably and where it is
difficult to debug the root cause--is to be avoided.

I was suggesting something like an opt-in, in the same way a programmer has to
use the keyword global, if they really want to import a command line
function.

Issuing a warning is also fine with me because it makes it obvious that there
is a potential issue, and it is up to the programmer to make the judgment
call.

Matlab, as usual, is of no help.  The following script is allowed (i.e., it
runs) and it emits no warnings, and the output is "Hello", not 0.14112.


1;
which sin
sin (3)

function y = sin (x)
    disp ('Hello');
end


I don't think the situation we are trying to address comes up very often so I
would only modify things if it were easy.  But, assuming it was easy, it would
be nice to get a shadowed warning message whenever a function is added to the
symbol table.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56881>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/