[Octave-bug-tracker] [bug #46493] Incorrect result from fscanf and scanf with %i format

[Lachlan Andrew]

Follow-up Comment #13, bug #46493 (project octave):

Rik, I didn't notice that those variables were private until I tried writing a
patch...

My understanding is that it is currently not possible to have a warning that
sets the state without issuing a message, which is what is really wanted here.
 I think the best solution is to address bug #41028 ("warning off" should
still set state, for Matlab compatibility) by having three states for each
warning: "on" (message and set state), "off" (set state, but don't message),
"disabled" or similar (neither message nor set state).  Then we could have a
warning for this that is "off" by default.

    _______________________________________________________

Reply to this item at:

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

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