[Octave-bug-tracker] [bug #57459] Dynamically loaded SuiteSparse functions should be moved to core

[Markus Mützel]

Follow-up Comment #4, bug #57459 (project octave):

I think I get your point now.
I don't know how those SuiteSparse_config settings are shared. Does Octave own
its own settings structure or is that structure shared among different
programs using SuiteSparse functions (i.e. are those settings thread local or
global)?
In any case, I agree that it would be safest to set the pointers each time we
call a SuiteSparse function that uses them. If we want to be nice to other
functions using SuiteSparse with different settings, we might want to reset
them to the previous values once we are done.
In the latter case (SuiteSparse_config share between threads/programs), I'm
not sure how that could be done in a thread-safe manner.

    _______________________________________________________

Reply to this item at:

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

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