[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #39703] test script with two outputs doesn't r
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #39703] test script with two outputs doesn't run all tests |
Date: |
Wed, 07 Aug 2013 15:08:52 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 |
Follow-up Comment #1, bug #39703 (project octave):
When %!shared variables are declared they are valid until the next %!shared
declaration. The test.m script doesn't know whether you used any of the
shared variables or not, but it prints them out in case they were used and had
a bearing on this particular test. Normally, this is exactly what you want
because the test format tends towards
%!shared x,y,z
%! ... declare x,y,z
%!assert (func (x), y);
%!test
%! tmp = func (x,y);
%! assert (tmp, z);
The %!assert or %!test block wouldn't make sense unless you also knew the
value of the shared variables x,y, and z. One could try to code a regular
expression to see if any of the shared variables were used in the code snippet
before printing them out, but this sounds like overkill.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39703>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/