In this version of Octave, “warning on” really enables all warnings (while this
was not the case in Octave 6, suprisingly; I think this used to be different
with even older Octave releases).
We therefore need to explicitly disable the Octave:array-as-logical warnings,
that is triggered by some internal Octave functions.
We also need to be careful to call “warning_config” instead of “warning on”
when restoring warnings to their default state.
It is now supported by the MATLAB editor (as of R2022a).
The old ASCII notation is left in some files that we copy as-is from other
sources (e.g. in the contrib/ and m4/ subdirectories).
The particles submodule is not updated at this point, because it is in an
inconsistent state.
[skip ci]
This is a workaround for Octave bug 46849. It complements commit
4c0b2e8c4e.
The workaround consists in moving the two problematic files to a subfolder
which is not in the path at startup. They will be added to the path later, at a
time when the Octave:shadowed-function warning has already been disabled by
warning_config.m.
Closes: #1817
Because of a bug, Octave wrongly complains that matlab/+pac/+bgp/{get,set}.m
shadow built-in functions (see https://savannah.gnu.org/bugs/?46849).
We disable the warning as early as we can after running the dynare command.
However the warning will nevertheless appear two times in a given Octave
session (the first time when the addpath to Dynare is done, the second time
when the dynare command is run).
- at the end of the computation, don't display all preprocessor warnings but
only their number
- also display if there has been a MATLAB/Octave warning (counting their
number does not seem feasible). Closes#181
- add new "nowarn" option to disable all warnings. Closes#301
Sébastien Villemot
Stéphane Adjemian (Charybdis)
Sébastien Villemot
sebastien