[Octave-bug-tracker] [bug #47543] segfault with warnings disabled in subfunction when all warnings disabled globally

[Lachlan Andrew]

Update of bug #47543 (project octave):

                  Status:               Confirmed => Patch Submitted        

    _______________________________________________________

Follow-up Comment #4:

The attached patch should fix the problem.  Thanks for the simple test case,
Mike.  I also plan to write a BIST for this, but want feedback first.

The code now does what I intended, but that is still not really the right
thing.  Issuing "warning <state> all" only changes the default state, so that
it doesn't disturb the "language-extension" warning.

This doesn't really affect Matlab compatibility, since the warning IDs are all
different and no command can be used on both platforms.  That means that the
team leaders can decide if "warning <state> all" should assign that state to
all warnings, or just to those not explicitly specified.

My personal choice would be to provide a mechanism to turn
"language-extension" off for core+forge functions, as was discussed at bug
#36743, particularly jwe's comment 9
[https://savannah.gnu.org/bugs/?func=detailitem&item_id=36743#comment9]. 
(Please overlook my intemperance in some comments in that discussion...)

I'd like to overhaul errors and warnings to give more flexibility than just
"on" and "off", but first I need to learn to stop submitting bugs :)

(file #36776)
    _______________________________________________________

Additional Item Attachment:

File name: bug_47543_warning_all.cset     Size:0 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47543>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/