Mikhail Katliar

Same issue with tiny bars in MATLAB R2019b.

@jgillis I need a quick fix for this. Do you think it is a good idea to add the following lines in `mem.h`: ```c #ifndef CASADI_INT_TYPE #define CASADI_INT_TYPE long long...

Having `casadi_int` as a macro in one place (the generated code) and as a typedef (`casadi_types.h`) in the other can create naming conflicts. It is probably better to change `casadi_int`...

There is still inconsistency in `mem.h` which prevents the generated code from compiling. For example, `casadi_decompress()` is declared as taking arguments of type `int*`: https://github.com/casadi/casadi/blob/f6023226b692317576a40d8986750b2cd8779433/casadi/mem.h#L70 but is called with arguments...

The target `X64_AMD_BULLDOZER` is still broken, although a year has passed and the reason now may be different. For example, the `blasfeo_dsyrk_dpotrf_ln()` function returns incorrect results.

> So it would be nice the `call()` method returns the string to caller. Or throw an exception to the caller, if the service also threw.

> We'll look into upstreaming those changes in the future (provided NoMagicAi is interested in that of course). @gavanderhoorn of course we are interested!

Sorry, wrong link. I have enabled issues on https://github.com/NoMagicAi/abb_librws, of course.

@herrvonregen we encounter the same problem from time to time, so if you find why it happens and how to fix it please submit a PR.

Thank you very much for your replies, now it is clear. Would it be possible to add this explanation somewhere in the docs?