> > If putting all the code into matrix.pmc is going to be a problem
I see another problem coming up which i dont have the exact solution to.
How are we going to fit operations like
det() ludcmp() inverse() solve() transp() and others into vtable.
By that i dont mean that they should exist in vtable, but that
they must be placed in functions in the existing vtable.
(Q) What vtable function should we call to get determiant?
(A) get_integer() is quite nice. Calling set I0,P0 and get determinant
value..
(Q) What vtable function ...... to get inverse?
(A) Now this one is really tricky. As i see it there isnt any suitable
vtable function for this. How are we going to solve
this?
I believe we need a generall interface for accesess on "custom"
pmc function. Functions should also be accessable to ops...
/Josef
