GitLab

Previously they were returned as 3-column matrices. But this was inconsistent
with the M-file mode.

We don’t support that compiler, and in any case it should support C99.

This is a preparatory step to allow use_dll with block decomposition.

Use 3-column format before calling sparse().

Ensure that the 3-column matrix is constructed in column-major order: data
locality will greatly improve performance once we implement use_dll.

Some evaluated blocks could be incorrectly merged, leading to wrong
results (e.g. blocks incorrectly marked as evaluable forward).

Bug introduced in 39407083

This is much more explicit.

Block decomposition: for “solve two-boundaries” blocks, move the iteration loop outside the dynamic file

Block decomposition: for “solve two boundaries” block, no longer compute “b” (-residuals+g1*y) in the dynamic function

Block decomposition: remove duplicate “periods” arg. to dynamic file of complete two-boundaries blocks

In the driver file, provide mapping between model local variables and indices in the temporary terms vector

The structures are M_.model_local_variables_{dynamic,static}_tt_idxs.

Ref. dynare#1722

Ref. dynare#1723

JSON output: when writing the model after computing pass, use TEF terms for (not derived) external functions

This is inconsistent with the way they are printed in equations (without
underscores).

The practice of appending underscores only makes sense in a MATLAB workspace context.

Also, do various other cosmetic/simplification changes.

Note that MSYS2 has now switched to zstd for compressing their packages.

Ref. dynare#1727

Rather use a single vector as in non-block mode.

By the way, change the order of output arguments in static functions, to be
closer to the dynamic ones.

Rather use a single vector as in non-block mode.

Should no longer be needed now that the minimal MATLAB version is R2014a.

We normally never arrive here, since MLV are not compatible with 'block'
option.