octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #38435] delete.m "max recursion depth exceeded


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #38435] delete.m "max recursion depth exceeded" in windows 1.2.0 package
Date: Thu, 28 Feb 2013 22:39:41 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6

Follow-up Comment #5, bug #38435 (project octave):

If in address@hidden the
line:


  output = com_delete (varargin{:});


is replaced by a simple


  com_delete (varargin{:});


it all works OK, both in 3.6.x and in (MXE compiled) 3.7.2+
I do not understand why, but it works. I also do not understand why "output =
" LHS apparently doesn't harm in the other functions in address@hidden

The Java message below is a red herring, it was just a next statement in one
of the io functions. The COM error occurred in a try-catch.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]