GitLab

New “with_epilogue” option of “shock_decomposition”, “realtime_shock_decomposition” and “initial_condition_decomposition”

Ref. dynare!1688

Ref. dynare!1688

issue #36

issue #36

issue #36

issue #36

Closes: dynare#1677

issue #36

#36

#36

Note that there is no equivalent of boost::filesystem::unique_path(), so I
implemented ModFile::unique_path() which does something similar.

allow the use of previously assigned variables in epilogue block in later equations in epilogue block

Introducing a new DataTree::getVariable() const method was necessary in the process.

In particular, it is necessary to turn back DataTree::AddVariable() into a
non-virtual method, because it is called from DataTree's constructor. Enforcing
the absence of leads/lags is now done using a new boolean DataTree::is_static.

Take advantage of the new copy constructor for handling
PlannerObjectiveStatement more elegantly.

Unfortunately it is not possible to implement *move* constructor / assigment
operators, because the reference ExprNode::datatree is not mutable.

The syntax makes clearer the distinction between a function call and an
initialization. Also, it prevents bugs due to implicit type conversions.

Incidentally, replace the IS_* macros by inline functions.

This code is broken since the temporary terms array changes. It is probably not
worth maintaining it.