[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave warnings
From: |
John W. Eaton |
Subject: |
Re: Octave warnings |
Date: |
Thu, 20 Sep 2012 09:18:03 -0400 |
On 20-Sep-2012, Judd Storrs wrote:
| A slightly different approach would be to change the available warning states
| from {"on", "off", "error"} to perhaps {"on", "off", "verbose", "error"}. So,
| for example
|
| warning on Octave:broadcast
|
| would behave as it currently does and to get backtraces you could
|
| warning verbose Octave:broadcast
That might be useful, but to request a stack trace, I think I would
use "backtrace" instead of "verbose". Also, Matlab doesn't work that
way, so it introduces an incompatibility. In Matlab, the "backtrace"
and "verbose" modes apparently only apply globally, not to individual
warning IDs. For example,
warning STATE MODE
in which STATE can be on, off, or query, and MODE can be verbose or
backtrace. I'm not sure what "warning query verbose" is supposed to
do. Octave should recognize these options now, but some of them have
no effect yet.
| Another option is to always emit a brief breadcrumb (not the full backtrace)
| for every warning. Something short and terse like a " (function:line)" suffix
| so that
Yes, that would be useful, and I think is what Matlab does now.
Patches, anyone?
jwe