Rule Object variables mistakenly being left in open state

[GoogleCodeExporter]

In InterpretedRuleInstance::addObjectVariable, canBeSpecified was mistakenly 
being passed as the leaveOpen argument to makeObjectVariableFromType(), as a 
result, all object variables created inside a rule were being left in an open 
state.

new variables are consistently left in a closed state after initialization, see 
ExprVarDeclaration::eval, where all variable declarations are processed, global 
and token vars are closed, rule vars are also supposed to be closed, but 
because of this bug, they were inadvertently being left open. This would leave 
to unexpected behavior at run time as the base domain of an object variable 
within a rule would fail to perform any prunning during propagation.

Original issue reported on code.google.com by javier.barreiro@gmail.com on 14 Jul 2011 at 7:27

[GoogleCodeExporter]

Original comment by javier.barreiro@gmail.com on 14 Jul 2011 at 7:29

• Changed title: Rule Object variables mistakenly being left in open state

[GoogleCodeExporter]

Original comment by javier.barreiro@gmail.com on 30 May 2012 at 5:26

• Added labels: Milestone-EUROPA-2.7
• Removed labels: Milestone-EUROPA-2.6

[GoogleCodeExporter]

The past tense and the code all suggest that this "issue" is fixed.  Closing 
this for now.

Original comment by miata...@gmail.com on 21 Aug 2014 at 10:59

• Changed state: Fixed