[Octave-bug-tracker] [bug #58686] Interpreter silently ignores inputs

[Rik]

Update of bug #58686 (project octave):

                  Status:               Need Info => Confirmed              

    _______________________________________________________

Follow-up Comment #2:

Just for reference, Octave does detect the situation if there is a return
value.  For example, with Octave-3.2.4


octave-3.2.4:2> x = do_nothing(3)
warning: do_nothing: some elements in list of return values are undefined
x = [](0x0)


And with the development version of Octave,


octave:2> x = do_nothing (3)
error: value on right hand side of assignment is undefined


But you are right that octave_value_lists are being shortened, and this is
both unexpected and probably wrong.

I used the debugger to set a breakpoint in assert.m to get an idea about what
the interpreter is seeing.

The code is


function assert (cond, varargin)


When I run 'test do_nothing', I find that nargin = 1 and cond = rand (3).  The
result of do_nothing(3) has been entirely removed.


    _______________________________________________________

Reply to this item at:

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

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