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

[John W. Eaton]

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

The forced_interactive function won't be a problem because it only touches
data managed directly by the application object and that is the very first
object that is constructed.

Yes, it is currently possible to cause a segfault if you use one of the static
functions that dereferences the application::instance pointer before an
application object is created, but that is not the way we use this class.

I could make the application class a singleton like others in Octave, but I'm
trying to head in the direction of eliminating those, not adding more!

Another option would be to fail a little more gracefully if someone were to
attempt using one of the static functions before creating an application
object, but I don't think that's necessary at the moment.


    _______________________________________________________

Reply to this item at:

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

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