Ian McInerney

To split out the interrupt routine for MATLAB from the main code, using a WIP branch, the interface will need to contain a C file with ``` /* * Implements...

The MATLAB-specific memory management code is: ``` /* Memory managment for MATLAB */ # include "mex.h" static void* c_calloc(size_t num, size_t size) { void *m = mxCalloc(num, size); mexMakeMemoryPersistent(m); return...

Will be fixed by https://github.com/oxfordcontrol/osqp-matlab/pull/37.

Sorry about that confusion. My second comment on the if statement guarding the call to the actual OSQP update function still needs to be addressed though, since only checking for...

> in principle a warm start with only x and without y is possible, but indeed the question is whether it makes sense ... The function to call if you...

Basically what I am saying we should do is have code before the call to `osqp_warm_start` like: ``` if ( mxIsEmpty(x) || mxIsEmpty(y) ) { mexErrMsgTxt("Both x and y must...

Hmm, according to the comment that header is only needed for the codegen component. I was wanting to move the code generation into the C library itself for v1 (so...

Thanks for doing this and sorry it hasn't been looked at until now. There is actually already a check in the Matlab class wrapper here https://github.com/oxfordcontrol/osqp-matlab/blob/master/osqp.m#L569 that is supposed to...

Please note that the crash when the matrix size isn't specified has been fixed in 0.6.2 released earlier this year.

This actually does look like an interface-specific issue. That backtrace (and the similar backtrace in #86) appear to be trying to directly access the structure before setup has been called...