Le 23/12/2012 16:26, Volker Braun a écrit :
I know of course that the runtime linker can resolve the symbol even if you didn't specify them at compile time, otherwise the dlopen()/dlsym() would never work. But in practice that means that you have to switch your libblas.so symlink all the time. Whenever you compile something you need the dumb blas, and when you run Sage you need the fast blas. What if you run cython() in Sage to access blas from C? How is that going to work if you have multiple Sage processes? What if Sage is installed system-wide and $SAGE_LOCAL/lib is not user-writeable?
My point is that as long as blas is a common api, you don't need to do anything to make it easy to change from an implementation to another.
Nothing forces you to change the blas from compile-time to run-time ; I really don't understand your objection : it's about being able to do something, not being coerced to do so.
What justifies adding a wrapper in the code when the linker is basically already one?
Snark on #sagemath -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
