On Thu, May 23, 2013 at 9:14 AM, Jonathan Wakely <jwakely....@gmail.com> wrote:
> I was wondering the other day whether we should put these checks on > trunk and enable them automatically when !defined(__OPTIMIZE__) FWIW, we keep this under a separate macro so we can turn it on or off independent of other build options. Our current code looks like this: #if !defined(__google_stl_debug_vector) # if !defined(NDEBUG) # define __google_stl_debug_vector 1 # endif #endif Keying off NDEBUG rather than __OPTIMIZE__ seems like a more consistent approach -- if you want assert()s, then you probably also want these checks. -- Paul Pluzhnikov
