(This is another post I've forgotten to answer completely.) On 9 March 2012 15:34, Alex Ott <[email protected]> wrote: > Thank you Mateuz > > Regarding build - we've used cmake -DBUILD_TYPE=Release, but assert > was left in binary...
As the comment says, the assertion is not a strong check, but for testing purposes: assert(sz < std::numeric_limits<unsigned short>::max()); // Not a strong constraint, for debugging only If it is annoying while testing your software with debug build of SOCI, then I see no problem with commenting it. If you get it caught in release build with NDEBUG=1, then it means the build is misconfigured, isn't it? For debug build, I'd keep the assert as it may be useful, but if it makes trouble in release mode, then the build should be fixed. Not sure what's happening there though. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
