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

[Mike Miller]

Follow-up Comment #6, bug #58296 (project octave):

> throw a warning when one tries to set a warning id that does not pre-exist

This seems like a nice idea, but is unenforceable. Any string with a colon in
it is a valid warning ID.

> I assumed that Octave:built-in-variable-assignment referred to masking a
built in variable or function

That warning ID is not used by Octave anymore, it could be removed or marked
as deprecated in the warning_ids list.

Once upon a time, this warning was only used to warn about specific built-in
variable names, like 'PS1' or 'save_precision', that I guess used to be global
variables but were changed into functions that you call like this to change
the value: PS1(">> "). It was never a generic warning for any variable that
shadows any function name.

    _______________________________________________________

Reply to this item at:

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

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