On Oct 27, 2010, at 4:45 AM, Waters, Anthony wrote:
So far it goes successfully through two steps of the optimisation and constraint testing. Unfortunately, it then crashes with a memory read error, which has me stumped.Has anyone got any bright ideas?
Markus Wendt, who developed a .NET plugin recently, pointed out a slight weirdness in the Windows interface: all of the NLopt functions are stdcall, EXCEPT for the callback functions (objective/constraints) which are cdecl. This causes a crash if you pass a stdcall callback.
I'm thinking of changing everything back to cdecl for the next release, since it sounds like most Windows stuff (.NET etcetera) can call cdecl functions.
Steven
_______________________________________________ NLopt-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/nlopt-discuss
