[Octave-bug-tracker] [bug #59451] Function handles become invalid if path to function is removed

[John W. Eaton]

Follow-up Comment #24, bug #59451 (project octave):

Markus:  If I understand correctly, the MOxUnit output is different because in
newer versions of Octave the following errors are available for catch blocks
to display:


skipped: resetting the warning state seems not to work (TODO: file a bug
report?)

skipped: <matlab.unittest.Test> class is not available


Previously, those messages disappeared but the tests were still skipped(?).

Also, the messages



failure: elements are not equal

First input: 1x1 logical
0

Second input: 1x1 logical
1
  assertEqual:70
(/net/devnull/scratch/jwe/build/octave-stable/MOxUnit/MOxUnit/assertEqual.m)
 
test_moxunit_util_platform_supports>test_moxunit_util_platform_supports_localfunctions_in_script:18
(/net/devnull/scratch/jwe/build/octave-stable/MOxUnit/tests/test_moxunit_util_platform_supports.m)


appear to be happening because tests/test_moxunit_util_platform_supports.m
assumes that Octave supports local functions in a script.  Looking at
util/moxunit_util_platform_supports.m, that apparently means

+verbatim
 'localfunctions_in_script'  - whether scripts called from a
                               function have access to local
                               subfunctions in that function
                               (Functionality removed in Matlab
                               2016a)



    _______________________________________________________

Reply to this item at:

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

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