[Octave-bug-tracker] [bug #39343] mexErrMsgTxt("") does not abort execution of script.

[anonymous]

Follow-up Comment #2, bug #39343 (project octave):

The mexErrMsgTxt() docu doesn't say anything about special treatment for empty
strings, so in that sense i expect it to treat an empty string just as any
other string. The current docu for the error() function otoh. explicitely
states that "...  If msgString is an empty string, the error command has no
effect. ...", so the difference between mex and m file api seems to be
intentional.

I can also confirm from testing that Matlab's mexErrMsgTxt() function behaves
like that since at least ancient Matlab V5.

That said, i seldomly pass an empty error string, which is why i only managed
to track down some weirdness in some corner case now, despite my toolkit being
ported to ocatve since multiple years, so maybe it would be enough to document
the difference?


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39343>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/