It maps column indices in the Jacobian returned by bytecode MEX in evaluate
mode (which only contains nonzero columns, but also incorporate recursive
variables), into column indices in the sparse representation (which has 3×n
columns for two-boundaries blocks and n columns for one-boundary blocks).
Columns unused in the sparse representation are indicated by a zero.

It would return an incorrect result. This had no impact except for debugging
information.

When parsing the FSTPG{2,3} opcodes, the bytecode MEX internally constructs a
Jacobian with as many lines as feedback variables. But the preprocessor would
also output instructions for filling derivatives of equations corresponding to
recursive variables in the “evaluate” mode, thus leading to memory corruption
in the bytecode MEX.

The two are now compatible, even though the bytecode representation will not be
used.

This is cleaner than using exit() or assert() for that purpose.

Currently defaults to 0.

This should have been in commit 0169240f.

Those options do not internally behave as the usual command options (which have
a “o_*” rule), so it makes more sense to treat them differently.

This is a restoration of the behaviour that was present in 5.x.

It is already available as a class member.

CI: fix linker issue with XCode 15 and add job for Homebrew arm64

See merge request Dynare/preprocessor!90

XCode 15 (on Ventura and Sonoma) has a linker issue, see https://github.com/mesonbuild/meson/issues/12282, workaround is to use ld_classic

For consistency with other such classes, since it represents the homotopy_setup
block.

Also enforce the path to x86-64 GCC.

Options for Bayesian IRF Matching in method_of_moments command

See merge request Dynare/preprocessor!85

Instead of crashing the preprocessor (because DataTree::DivisionByZeroException
is not caught), just abort the normalization and mark it as failed.

Ref. #92

Those models do not have as many variables as equations, and this case is not
supported by bytecode.

The present commit is an improvement over commit
a8ea57dd, which had already removed bytecode
for the planner objective model.

“clearvars” has been implemented in Octave since version 5.

The preprocessor would try to write bytecode for the planner objective. But
bytecode only works when there are as many endogenous as equations, which is
not the case for the PlannerObjective object derived from StaticModel.

occbin.solver: do not pass and return full oo_ structure

See merge request Dynare/preprocessor!87