[Octave-bug-tracker] [bug #36288] Accessing variables in some recursion gives wrong values if handle to private function is set.

[Olaf Till]

Follow-up Comment #3, bug #36288 (project octave):

A similar problem is still present in Octave-3.8.0, revision ab775508dff9,
although it can't be triggered with the original example. Inside an if-block,
checking in its condition if a certain variable has a certain value, the value
of the variable seen from a debug prompt by typing the variable name is
different. Again, there is recursion involved, but this time only further up
in the call-stack, the function where the problem shows up is not called
recursively (but repeatedly).

Last time I could boil down the problem to a simple example, but that was much
work. It should be easier now to check out the revision in which the original
example triggered the bug and see there what happens, assuming it had the same
reason.


    _______________________________________________________

Reply to this item at:

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

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