Joel Andersson
Joel Andersson
You can fix it by patching swig, or by writing your own typemaps (as I did).
`std::map` is a tricky thing to get working. It's not a 100 % match with MATLAB structs (far from it) and you'll get into troubles if you want to have...
> Was this issue supposed to be fixed by d886034de67bcf03562cfabcec8248fdf591cc07 ? No, I think that was just to resolve compilation errors.
The casadi.i file redefines _all_ of the typemaps we use, using a combination of typemaps, fragments and defines. I'm not sure if that's the way forward for you though. We...
Sounds like it's not implemented properly. In CasADi we have a output typemap for it. So the user never works directly with it - it gets converted to a MATLAB...
OK, it's probably a reference counting thing. It needs to keep a reference to the original `vector` in order to do things like `mystruct.x(3) = 3`.
It's probably fixable with a moderate effort. But someone has to do it.
It's ambiguous, no? Why would you want support this?
Probably a tricky thing to implement...
`double(A)` is supposed to mean "convert to double storage", not "convert to a double scalar", so `%rename("double") class::operator double` is not necessarily the answer. Anyway, in many cases, `%rename("double")` will...