> I think, we can just warn people about changes in API and ask them to
> change their own scripts.
> And, of course, we'll change ./examples/* files and forget about those
> functions.
>
I will add the warning wrapper, not difficult. Just one more macro ;-)
> > Do we use Matrix3r*Matrix3r somewhere?
>
>
> No, but it is a meaningful operation, so no reason to not
> support it,
> right? (In c++ it is used in Cell BTW)
>
> In this case, maybe, it is easier to write this function-wrapper from
> scratch?
Sorry, I don't understand what you mean. With the macros in
py/miniWm3Wrap/manualWrap.cpp, it is as simple as
EIG_OP2(Matrix3r,__mul__,*,Matrix3r)
and then
.def("__mul__",&Matrix3r__mul__Matrix3r)
No real problem.
Cheers, v.
_______________________________________________
Mailing list: https://launchpad.net/~yade-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp