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

[John W. Eaton]

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

What is needed to reproduce the error?  I don't see the problem.

To decide how to properly fix this, I need to see where the calls are
happening before the interpreter is created.

I don't think we can simply start the interpreter at any random time.  I
initially wanted to start it it first and pass it as an argument to the
application object, but that caused strange errors later with graphics objects
when using the GUI version of Octave.  I didn't fully investigate, but I think
it was an issue with threads.


    _______________________________________________________

Reply to this item at:

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

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