Waldek,
The point is that real code computes sizes, variable lists etc via functions and compiler should cope with that.
Well, as I said, my approach is to design things in a way that does not involve functions. Unfortunately, one has to cope with the current Algebra library which is not perfect in this respect.
Anyway, the usual approach would be to remove such potential dependencies and function parameters have to be constant in context. The latter can usually be achieved by introducing a function layer that get's all the type parameters as arguments.
Of course, that doesn't solve the problem that in some cases there is an inherent dependency between the arguments. My approach would be to improve the library and remove such dependencies whenever possible. But that is a huge task and already your an my opinion differs.
I think, I'm going to invest some more time in improving the test framework in FriCAS (before modifying Algebra). Only yesterday I learned how you seem to test regression via the .output files. That all should become a simple "make check" that returns a summary of which tests succeed and which failed.
Ralf -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fricas-devel?hl=en.
