id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2599	Handling of (tuple) = f(...) when solving non-linear	Willi Braun	probably noone	"Examples like following were handled wrong in SimCodeUtil:
{{{
model TupleNonLinear
function ftest
  input Real a;
  output Real b;
  output Integer c;
algorithm
  b := 0;
  for i in {1} loop //prevent inlining
    b := b + sin(a);
    c := integer(a);
  end for;
end ftest;

  Real a;
  Integer c;
  Real x,z;
equation
  der(x) = sin(a + time);
  (x,c) = ftest(a);
  z = if c>=1 then 10 else 0;
  annotation (experiment(StopTime=2));
end TupleNonLinear;
}}}
We try to solve the equation
(x,c) = ftest(a) non-linear for
{a,c} but actually only a should be solved
non-linear and c can be calculated then directly."	defect	new	high	Future	Backend	trunk