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

[Markus Mützel]

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

                 Summary: Dynamically loaded SuiteSparse functions should be
moved to core
                 Project: GNU Octave
            Submitted by: mmuetzel
            Submitted on: Sun 22 Dec 2019 09:49:05 AM CET
                Category: Interpreter
                Severity: 2 - Minor
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

See jwe's comment #19 in bug #57435:
> If locking amd.oct avoids the problem, then maybe we should just move that
function to corefcn instead of defining it as a .oct file in dldfcn.  The
suitesparse libraries are always linked with liboctave if they are available
so there is no real point in dynamically loading functions that depend on that
library.
> 
> If we always load suitesparse libraries if they are available, then we could
also refactor the way that suitesparse config is handled as the comments in
SuiteSparse_config.h recommend.  Instead of attempting to initialize those
function pointers on demand, we could do it once at startup.





    _______________________________________________________

Reply to this item at:

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

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