On Sun, 7 Jul 2013, Riccardo (Jack) Lucchetti wrote:
On Sat, 6 Jul 2013, Allin Cottrell wrote:
> Um, no, reversing the default is not good. We want gretl to halt on error
> unless "catch" is used -- which is the current default.
>
> To explain just a little more, the reason I don't like the ability to turn
> halt_on_error off is that it's likely to give rise to cascades of
> (increasingly incomprehensible) errors. A script writer should figure out
> if any commands might fail for good reason and, if so, use "catch" on them
> -- and not just tell gretl to keep going regardless of how messed up things
> are.
Uhm, point taken. Let's do as you say.
Actually, we could take the spirit of your suggestion (i.e.
gradualism) in this way:
1) In the next release, keep "set halt_on_error off" working as at
present but print something like
Warning: 'set halt_on_error off' is deprecated. Please use
'catch' to trap errors instead.
2) In the following release, remove it.
Allin