On May 26, 2010, at 1:10 PM, Dmitri Tchikine wrote:
(On this note though, it would be good if memory management inside the library is also based on smart/shared/auto pointers - in the current design any exception thrown inside the caller's function would result in memory leak)
I strongly prefer to keep NLopt a pure C library to make it easier to call from as many languages & compilers as possible.
What I may do is to allow the user a way to halt the optimization cleanly. That way, you can catch any exception in your C++ objective function, halt the optimization, and then do whatever you want.
_______________________________________________ NLopt-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/nlopt-discuss
