[Octave-bug-tracker] [bug #31815] speed demos no longer work since version 3.2.3

[Rik]

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

I'm intrigued, but not surprised, that you had a few crashes during the
testing.  There is a memory leak somewhere in the parser dealing with
functions which I found by running fntests.m under valgrind.  The small
function you attached to this bug report also provokes a memory leak when run
under valgrind.  I will report those experiences at bug report #31644 which
deals with memory leaks.

Perhaps an easier path than re-writing demo.m would be to re-write speed.m? 
We generally use demo code where it is not possible to use test code, such as
the plots.  Here, we could promote one of the demo blocks into the texinfo
section just as an example, delete the other, and write a %!test block to
ensure that speed.m works.

This supposes that there are not too many other instances of demos with
subfunctions.  If there are then I suppose the correct approach is to deal
with demo.m and subfunctions.

    _______________________________________________________

Reply to this item at:

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

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