It seems MATSHELL implementation is a bit broken. If I'm not wrong, if
a user set the operations MOP_ASSEMBLY_END, then the use of the
automatic MatScale/MatShift would lead to unexpected result...

Should this operation be managed the same way as
mult/multtranspose/get diagonal currently is, that is, by backupping
the user provided function pointer?

BTW, sorry if I disturb you asking for making changes that seems
trivial, but I really do not like to change any line of code after
knowing your opinion.

-- 
Lisandro Dalc?n
---------------
Centro Internacional de M?todos Computacionales en Ingenier?a (CIMEC)
Instituto de Desarrollo Tecnol?gico para la Industria Qu?mica (INTEC)
Consejo Nacional de Investigaciones Cient?ficas y T?cnicas (CONICET)
PTLC - G?emes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594


Reply via email to