[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #32296] matlabbatch: equivalent subscript assi
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #32296] matlabbatch: equivalent subscript assignments produce unequal results |
Date: |
Mon, 31 Jan 2011 10:48:58 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110107 Iceweasel/3.5.16 (like Firefox/3.5.16) |
Follow-up Comment #1, bug #32296 (project octave):
Jaroslav, I'm copying you on this report because you have worked on this part
of Octave much more than I have lately, so I'm hoping you will have some
insight here.
It seems that this problem is related to the following change:
http://hg.savannah.gnu.org/hgweb/octave/rev/b2b8ed43b922
which was made in response to the following bug report:
https://mailman.cae.wisc.edu/pipermail/help-octave/2009-April/034731.html
The change added a check to see whether octave_value::subsasgn was called
from the "builtin" function, and if so, the subsasgn method lookup is skipped.
Maybe this was not the right fix, but it avoided the reported problem.
In your case, the cfg_repeat and cfg_exbranch subsasgns call subsasgn using
the "builtin" function, but they should perform the method lookup, and if they
do, I think Octave does the right thing for your code.
However, simply removing the check for called_from_builtin in subsasgn brings
back the earlier problem.
So I don't know how to solve both problems at the same time. What is the
appropriate check that should be made here to avoid the recursion in one case
and to allow the method lookup when it is needed?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?32296>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/