[Octave-patch-tracker] [patch #8119] Allow variable tolerance and improve error messages for assert.m script

[Dan Sebald]

Follow-up Comment #3, patch #8119 (project octave):

Yeah, I suppose you are right.  A vector containing only the different values
with no position information is somewhat arcane.

Printing zeros for entries that match is easy enough, but it's a little more
confusing than, say, "*".  I better way to show the elements that are
different would be to display the contents similar to the current "display()",
but make the font color for those elements that are different red.  Not sure
that is possible right now.  A simple way to do this might be modifying
"display()" to have optional input color matrices the same dimensions as the
matrix, e.g.,:

display (X, R, G, B)

The color used for a particular element is gotten via the corresponding
elements in R, G and B.

Another approach that might be more condensed would be to write the contents
of the matrices that are different as text strings similar to what a cell
looks like.  That way, people will be used to the format.  Your example would
look like:


Expected:

exp =
{
  [2,1] =  2
  [1,2] =  3
}

but got:

obs =
{
  [2,1] =  3
  [1,2] =  2
}


As far as the stack trace depth, I typically only ever use the first level,
i.e., the first trace statement following the error message.  It would nice,
generally, to have a configuration option for the number of levels/calls to
display in the trace.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8119>

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