Message157070
| Author |
max |
| Recipients |
max |
| Date |
2012年03月29日.17:07:11 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1333040831.85.0.92124341394.issue14445@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Currently -O optimizer flag disables assert statements.
I want to ask that more fine-grained control is offered to users over the assert statements. In many cases, it would be nice to have the option of keeping asserts in release code, while still performing optimizations (if any are offered in the future). It can be achieved by removing the "disable assertions" feature of the -O flag, and instead adding a new flag that does nothing but disables asserts. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年03月29日 17:07:11 | max | set | recipients:
+ max |
| 2012年03月29日 17:07:11 | max | set | messageid: <1333040831.85.0.92124341394.issue14445@psf.upfronthosting.co.za> |
| 2012年03月29日 17:07:11 | max | link | issue14445 messages |
| 2012年03月29日 17:07:11 | max | create |
|