[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #41028] warning off shouldn't affect lastwarn
From: |
Lachlan Andrew |
Subject: |
[Octave-bug-tracker] [bug #41028] warning off shouldn't affect lastwarn |
Date: |
Fri, 04 Dec 2015 01:40:20 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110422 Ubuntu/8.04 (hardy) Firefox/3.6.17 |
Follow-up Comment #6, bug #41028 (project octave):
I have freshened the patch.
One caveat with changing the behaviour of "warning off" is that there are many
warnings that are off by default but are thrown by core code like "help".
An alternative to this patch is simply to rename "quiet" to "off" and to
rename "off" to something like "nothing". That keeps Matlab compatibility and
the current flexibility.
I have two related gripes. Please let me know if they should be separate bug
reports:
1) Is there a comand to reset the warning status to the original setting, with
a dozen or so warnings "off"? If not, I think there should be.
2) The documentation should not recommend "warning(error)", because it breaks
commands like "help", without which it is hard to find out how to fix it. I
propose adding the keyword "active" as an alternative for "all", but that does
not affect warnings that are off, and making that the default set of warnings
when none is specified.
I'm happy to write patches for these if they are approved of.
(file #35639)
_______________________________________________________
Additional Item Attachment:
File name: bug_41028-warn-quiet-freshened.txt Size:3 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?41028>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #41028] warning off shouldn't affect lastwarn,
Lachlan Andrew <=