-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop 1.0 #55
base: master
Are you sure you want to change the base?
Develop 1.0 #55
Conversation
…es_test (polish -> polishing)
…s through the API. Also reversed the change to .gitmodules.
…, update_codegen_defines. Added osqp_struct_codegen_defines.cpp and updated osqp_struct.h. Updated the relevant .m files (codegen.m still needs work). Minor refactoring to osqp_mex.cpp.
if (!strcmp("delete", cmd)) { | ||
osqp_cleanup(osqpData->solver); | ||
destroyObject<OsqpData>(prhs[1]); | ||
// Warn if other commands were ignored | ||
if (nlhs != 0 || nrhs != 2) | ||
mexWarnMsgTxt("Delete: Unexpected arguments ignored."); | ||
return; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused about this. During the constructor ("new"), I dynamically create a new OSQPCodegenDefines object (see Line 159). Seeing how osqp_cleanup destroys osqpData->solver, I thought I would have to free osqpData->defines manually. However, when I did that, the program crashed because destroyObject tries to destroy the already freed memory. What I don't understand is why this doesn't happen with osqpData->solver, which is freed by osqp_cleanup.
a7a5e89
to
391fe8f
Compare
Develop 1.0 codegen
…les that do not contain the word "License" in them.
Added support to codegen, changes to c_source, memory,