[Octave-bug-tracker] [bug #58296] Weird warning behaviour - regression bug?

[Rik]

Update of bug #58296 (project octave):

                Severity:               2 - Minor => 3 - Normal             
                Priority:                 3 - Low => 5 - Normal             
              Item Group:           Documentation => Regression             
                  Status:                    None => Works For Me           
                 Release:                  6.0.90 => 5.2.0                  
        Operating System:                     Any => GNU/Linux              
                 Summary: Improve description of warning state => Weird
warning behaviour - regression bug?

    _______________________________________________________

Follow-up Comment #2:

Case 1 : non-existent warnings

Octave doesn't have a full list of all warnings that can ever be produced
because the list is dynamic.  You could open up an editor and write a new
m-file which defines a new warning ID and Octave has no way of knowing about
this.  Similarly, you could use addpath to add a whole directory of new
functions, but in order to understand whether a new warning ID had been
declared would require parsing every single function and storing the
information away somewhere.  

Incidentally, Matlab behaves the same as Octave.  Try something like


 in that it allows you to query non-existent warning IDs.  However, they take
the opposite position about whether they are enabled and assume that the
unknown ID is in the 'off' state.  Octave could change that default easily
enough.

case 2



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58296>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/