[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55939] 'dbstop if error' stops in function st

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55939] 'dbstop if error' stops in function str2num, when no error is present
Date: Sun, 17 Mar 2019 17:37:30 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.75 Safari/537.36

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')

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:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]