[Octave-bug-tracker] [bug #55254] clear all crashes when variable from oct file class is displayed in workspace

[John W. Eaton]

Follow-up Comment #9, bug #55254 (project octave):

How many other packages define new octave_value types?

And yes, something needs to be done to prevent .oct files from being unloaded
while objects of the new octave_value types they create exist in the Octave
interpreter.

I'm willing to try for a better fix that doesn't require modifying user code. 
Do you see a way to do that?

Is there some way to know that an octave_value is created inside a .oct file? 
Maybe we could make the association when a new data type is added to the
"typeinfo" list?  I suppose that counting all instances of a particular type
could be done in the octave_base_value constructors and destructors, but that
adds (a very small) overhead to copying all octave_value types, not just ones
that are dynamically loaded.  Is it worth trying to avoid that cost for
built-in types by having dynamically loaded octave_values derive from an
intermediate class instead of octave_base_value?  Maybe that would be the
simplest thing as the constructor for that new class could also handle the
registration/association of the type with the shared library that is loaded?



    _______________________________________________________

Reply to this item at:

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

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