[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: message ids for warnings and errors
From: |
John W. Eaton |
Subject: |
Re: message ids for warnings and errors |
Date: |
Wed, 7 Dec 2005 20:41:33 -0500 |
On 7-Dec-2005, Paul Kienzle wrote:
| ~/cvs/octave/scripts$ grep -h "^ *warn_" */*.m */*/*.m | sed -e"s/^
| *//;s/ *= */ = /" | sort | uniq
|
| warn_empty_list_elements = 0;
| warn_empty_list_elements = save_warn_empty_list_elements;
| warn_fortran_indexing = 0;
| warn_fortran_indexing = wfi;
| warn_str_to_num = 0;
| warn_str_to_num = tmp;
|
| ~/cvs/octave/scripts$ grep -l "^ *warn_" */*.m */*/*.m | wc
| 16 16 357
Since these appear to set the variables to what are now default
values, I'd be in favor of simply removing them.
| Similarly, octave-forge has 27 instances, including
|
| warn_divide_by_zero = 0;
| warn_divide_by_zero = wdz;
|
| Maybe warn could have another state 'expected' which
| suppresses the warning in the local scope?
I think I'd rather avoid the extra complexity. But maybe you see a
simple way to imlement it?
jwe
- Re: message ids for warnings and errors, (continued)
- Re: message ids for warnings and errors, Quentin Spencer, 2005/12/06
- Re: message ids for warnings and errors, John W. Eaton, 2005/12/06
- Re: message ids for warnings and errors, Stefan van der Walt, 2005/12/07
- Re: message ids for warnings and errors, John W. Eaton, 2005/12/07
- Re: message ids for warnings and errors, Paul Kienzle, 2005/12/07
- Re: message ids for warnings and errors, John W. Eaton, 2005/12/07
- Re: message ids for warnings and errors, Paul Kienzle, 2005/12/07
- Re: message ids for warnings and errors,
John W. Eaton <=
- Re: message ids for warnings and errors, Paul Kienzle, 2005/12/08
- Re: message ids for warnings and errors, Stefan van der Walt, 2005/12/09
- Re: message ids for warnings and errors, Paul Kienzle, 2005/12/09
- Re: message ids for warnings and errors, Paul Kienzle, 2005/12/07
- Re: message ids for warnings and errors, John W. Eaton, 2005/12/07