05-21-2009, 02:16 PM
Quote:I will put some more checking, but since this will slowdown array/string accesses, I think It could be a good idea to put some compiler option to enable/disable array/strings boundary checks. Once the program is debugged, you can recompile disabling it.
I really like this idea for testing. If it throws an error at that point, it's very useful for debugging - but correct code shouldn't do that. I like the idea of a
-nodebug option to make for faster code, at the user's risk :-)
(perhaps this could be part of the optimization system, so -O3 does this?)