Unfortunately, getting rid of the library asserts eliminates all the
asserts in wxWidgets, which are quite useful, along with heap
corruption checks and all the memory leak detection in the libraries..
Brendan O'Connor wrote:
On 9/17/05, John Anderson
<[EMAIL PROTECTED]>
wrote:
Adding
library asserts, python asserts and talkback to release is
equivalent to adding talkback to debug.
Always running the debug version doesn't makes sense for performance
reasons.
Another option: give the end-user release python asserts but NOT
library asserts. Running without C++ debug libraries but with
python asserts has just fine performance -- that's what I always did
when developing python parts of chandler. (knock off the -O
inside release/RunChandler and RunPython). An end-user release
configured like that would get lots of useful crash info, though not
for everything.
Unless it's the case that python -O actually optimizes... I was under
the impression that the main thing it did was turn off asserts.
Brendan
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
|
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
