On Wed, Aug 12, 2009 at 12:04 PM, Jonathan Guyer<[email protected]> wrote:
> I think the issue is that T is a solution variable, not the result of an > operation, so there's no evaluation to do. T.getValue() just returns > T.value, which is a reference to an array. When the value of T changes (e.g. > via T.setValue()), the contents of T.value are changed, but the reference > remains the same (it's the same array object). d['T'] ends up holding a list > of identical references to T.value, and so they all see the most recent > value stored. In a sense that is how it should work. A true evaluation creates a new array as does a copy. Should "getValue()" be creating a copy if it doesn't do an evaluation? -- Daniel Wheeler
