[Octave-bug-tracker] [bug #55939] 'dbstop if error' stops in function str2num, when no error is present

[Mike Miller]

Update of bug #55939 (project octave):

                Severity:              3 - Normal => 2 - Minor              
              Item Group:        Unexpected Error => Matlab Compatibility   

    _______________________________________________________

Follow-up Comment #3:

I think it would be useful to know some more details in order to proceed to
ensure that we don't break something else.

* Does Matlab break to debug mode if a function calls 'eval' with a string
that causes an error *not* inside of a 'try'? IOW does our 'eval' function
need to be fixed?

* Would adding a 'try' to 'str2num' break any other compatible behavior with
'str2num'? As I understand it, we have to use 'eval' to be compatible with
Matlab, but are there corner cases where 'str2num' might have a side effect
that 'try' would suppress?

With the following function testfunc.m:


function testfunc()
  eval('1z', '1')
end


Does 'dbstop if error' stop on the 'eval'?

It would also be much better if we could have someone test with a current
version of Matlab.

    _______________________________________________________

Reply to this item at:

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

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