[Octave-bug-tracker] [bug #48494] Current Dev access application functions before initialization

[John W. Eaton]

Follow-up Comment #3, bug #48494 (project octave):

OK, I think I see how this can happen if a warning message is printed (or
possibly other things happen) before the interpreter is ready.  But if the
interpreter isn't ready, I think it's safe for the application::interactive
function to just return false.  And for the one that sets the value to do
nothing, since it isn't really useful to try to make a nonexistent interpreter
interactive...

I checked in the following changeset:

http://hg.savannah.gnu.org/hgweb/octave/rev/4e770056f74a

    _______________________________________________________

Reply to this item at:

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

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