Waldek, While you are looking at scene.spad.pamphlet perhaps you may like to look at some tidyups and additions to the code and additions to (inline and literate) documentation that I have put here:
https://github.com/martinbaker/fricas/blob/master/src/algebra/scene.spad.pamphlet If you agree with these changes they would need to be consolidated with your changes (for instance I think you have removed the _ before a ! in a name and stuff like that). Would you do the consolidation or would you like me to attempt it? > But there is: code in category part will use functions in the > domain. Of course each such function must appear in category > export list, but definition may came from domain. > > There is no OO-dispatch because Spad values do not carry > type information. But when you use code in category part it > knows on behalf of which domain it is running and calls functions > from this domain. So there is dynamic dispatch, just different than > OO-dispatch. This is widely used in the algebra. Yes, I was probably getting errors because I was thinking in an OO way as usual. I was assuming that the functions called in the category would need to be declared in the category even if they are not defined (abstract in my terms) so that the category can be type-checked without knowing about the domains that might extend it. Is that what 'category export list' does? This gets especially confusing to me when these functions refer to % and have % as parameter. Are you going to make these changes? (it might be safer if you did) Martin -- 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.
