Expression enumeration with static variables about acado HOT 6 OPEN

I again totally agree, these global counters have been a handicap that is getting only worse also for developing the code, since things start probably only depending on it more and more..
Since I had the issue myself once, I can propose a quick fix if you are interested:
you can reset the counters at the end of your 'code generation code' which turns it into something more or less modular.. ;-)

But in any case, I believe it would be worth it to spend the effort getting rid of these global counters if possible ! What does the rest think?
Maybe it is also better to assign these issues to a certain milestone..

from acado.

This is an inherent property of AD within ACADO -- I am referring to the static variables. I agree this is not the smartest way to deal with enumerating expressions, and whoever is willing to work on AD within ACADO is welcome.

From what @ghorn says it looks to me that there is an elegant workaround in python.

Bindings are the separate issue, not related to the aforementioned issue. What I would like to see is SWIG in ACADO, something maintainable.

Those can be set as a task for a milestone, and I would close this issue.

from acado.

I don't fully understand what you changed the name of this issue to. Are DifferentialState / Control / etc. incrementing static counters? Or is this only internal to AD?

from acado.

@ghorn You can study the class inheritance tree starting from Expression class if you want to understand this matter. Those classes hold static counters. Function like classes use those enumerations.

from acado.

Hey Rien, can you give me a little code example which shows how to reset the counters?

from acado.

sure, it looks like this depending on which ones you want to reset:

Control dummy1; dummy1.clearStaticCounters();
DifferentialState dummy2; dummy2.clearStaticCounters();
Parameter dummy3; dummy3.clearStaticCounters();
IntermediateState dummy4; dummy4.clearStaticCounters();
...

from acado.