[Octave-bug-tracker] [bug #62829] "quiet" warning state is undocumented

[Markus Mützel]

Follow-up Comment #5, bug #62829 (project octave):

In Matlab R2022a:

>> nchoosek (100, 50)
Warning: Result may not be exact. Coefficient has a maximum relative error of
1.6875e-14, corresponding to absolute error 1702580784238102. 
> In nchoosek (line 121) 

ans =

   1.0089e+29

>> lastwarn

ans =

    'Result may not be exact. Coefficient has a maximum relative error of
1.6875e-14, corresponding to absolute error 1702580784238102.'

>> lastwarn('test')
>> lastwarn

ans =

    'test'

>> warning off;
>> nchoosek (100, 50)

ans =

   1.0089e+29

>> lastwarn

ans =

    'Result may not be exact. Coefficient has a maximum relative error of
1.6875e-14, corresponding to absolute error 1702580784238102.'

>> lastwarn('test')
>> warning on quiet
Error using warning
Unknown setting or incorrect message identifier 'quiet'.


So, it looks like `warning off` in Matlab behaves like `warning on quiet` in
Octave.
Matlab doesn't understand `warning on quiet`.


    _______________________________________________________

Reply to this item at:

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

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