On 19.01.2023 16:48, Cottrell, Allin wrote:
On Thu, Jan 19, 2023 at 9:52 AM Marcin Błażejowski
<marcin(a)wrzosy.nsb.pl> wrote:
> On 19.01.2023 14:47, Cottrell, Allin wrote:
>> Or more efficiently:
>>
>> outfile null
>> # do stuff silently
>> end outfile
> Well, it works of course but for me it is a trick rather than a true
> solution. It is because the message does not come from triggered command
> but from underlying apparatus. So from my point of view suppressing any
> messages from optimizers by 'set' command to silent/quiet/whatever would
> be better.
My proposal here would be to modify the effect of "set warnings off"
to set all warnings off -- not just, as at present, to turn off
warnings regarding NAs produced by genr.
(There would be a warning in the doc for this setting!)
Sounds good!!!
My feeling is that neither --quiet nor even --silent as applied to
individual commands should suppress warnings; they're about reducing
or eliminating regular output.
Ok. But printing warnings in numerical methods (like optimizers) might
be seen as some kind of debugging. If so, suppressing any messages could
be an option.
Marcin
--
Marcin Błażejowski