[Octave-bug-tracker] [bug #58296] Improve description of warning state

[Markus Mützel]

Update of bug #58296 (project octave):

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

    _______________________________________________________

Follow-up Comment #1:

Maybe there is some confusion on how Octave's warning system works.
Essentially, a user can emit a warning with any id (following some rules
though). So it is impossible to list all imaginable warnings with their
respective state.
Instead, the default warning state applies to all warning ids unless the
respective state is explicitly changed.

"warning on all" resets all warning ids to the default and sets the default to
"on".

Maybe we could transform this report into a documentation bug.
It would be very much appreciated if you could help improve the documentation
to better describe the behavior. Patches are always welcome.

The "Octave:shadowed-function" warning is also much more specific than one
might expect. It is only emitted when the user changes to a directory that
contains a function that shadows a core function or when such a directory is
added to the search path. E.g. in a folder where you have write access:

fid = fopen ("clear.m", "w");
fprintf (fid, 'function clear(), disp ("test"); endfunction\n');
fclose (fid);
path (path);


Variables shadowing core functions (or even command-line functions) don't
trigger the warning.
This could also be better documented.

    _______________________________________________________

Reply to this item at:

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

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