[Octave-bug-tracker] [bug #56419] Implementation of newline

[Rik]

Follow-up Comment #8, bug #56419 (project octave):

For %!assert statements the convention is to remove the semicolon because it
is unnecessary.  For %!warning and %!error it is occasionally necessary to
have a semicolon in order to suppress output.

There are some good examples directly from the newline implementation.

For example, at the command line


[a, b] = newline ()
a = 

error: element number 2 undefined in return list


Now make this a BIST test in a file tst_err.m


%!error [a, b] = newline ()


When running the tests I get extraneous output


test tst_err.m
a = 

PASSES 1 out of 1 test


Now, add the semicolon


%!error [a, b] = newline ();


and re-run


test tst_err.m
PASSES 1 out of 1 test


It isn't always necessary though.  The newline function, for example, throws
an error immediately if there are any arguments to the function.  This happens
before any return value is assigned.  So for the BIST test below, no semicolon
is required


%!error [a,b] = newline (1)



test tst_err.m
PASSES 1 out of 1 test


At the end of the day, I try not to use semicolons, but occasionally am forced
in to it by circumstances.


    _______________________________________________________

Reply to this item at:

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

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