|
| From: | Mike Miller |
| Subject: | [Octave-bug-tracker] [bug #53587] Disabling an undefined warning ID should give an error |
| Date: | Mon, 9 Apr 2018 03:05:20 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 |
Update of bug #53587 (project octave):
Status: None => Need Info
_______________________________________________________
Follow-up Comment #1:
Do you mean invalid rather than an undefined warning ID? What are defined
warning IDs? Doesn't that imply some kind of central registration point for
all warning IDs? The way I understand it, any user function can define any
arbitrary warning ID.
We could raise an error for some invalid warning identifier, for example
>> warning off 1234
error: warning: '1234' is not a valid warning identifier
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53587>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |