Peter N. Lundblad wrote:
>On Tue, 9 Nov 2004, [UTF-8] Branko �^Libej wrote:
>
>
>
>>Julian Foad wrote:
>>
>>And I disagree with the idea that a "debug" version of the code do more
>>checking than a "release" version, except where it really does check
>>"can't happen" conditions. But even then I'm sceptical, although I have
>>put asserts here and there in our code.
>>
>>
>>
>I aggree. Therefore, I don't define NDEBUG even for non-debug builds. I
>never understood why that's the default on some Windows build systems.
>
>
Because Visual C comes with two versions of the runtime library, a
"release" version -- usually present on all boxes -- and a "debug"
version. As you can imagine, only the debug version actually contains
runtime support for assert, so if you don't define NDEBUG in the release
build, your code doesn't link... At least, it used to be that way. Our
generated project files do define NDEBUG.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 9 21:57:29 2004