From maintainers-request at octave dot org Wed Dec  7 19:41:39 2005
Subject: Re: message ids for warnings and errors
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Paul Kienzle <pkienzle at users dot sourceforge dot net>
Cc: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>,         octave maintainers mailing list <maintainers@octave.org>
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