- you already know @Domain, that good solution
I would also have suggested that, but, honestly, I do not like it so much. And usually prefer to give the interpreter other hint on how to choose the right function.
- you may use different names depending on type, for example 'urand01_rv', 'urand01_cv', etc.
This usually better. It could also make sense (if this fits your idea) to write a package that is parametrized by the vector domain. Then you would simply package-call the right function via the urand01$YourPkg(JCF64VEC).
I'm not saying this is better or worse, it is just that not only the interpreter is confused. When you will read your code in 2 years, you will probably have a hard time to figure out from your code what the program actually does, i.e. which function was chosen, if this is not made more explicit. So I would say, not only help the interpreter to do the right thing, but also the user to understand your code without having to explicitly run it.
Ralf -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/fricas-devel/1a493942-d9bc-7d41-9930-0d659765e9a1%40hemmecke.org.
