Well I was referring to gcc actually, since it's a much better and extremely
helpful compiler when it comes to error-checking your code. But msvc has it
too:
configuration properties
C/C++
General
treat warnings as errors
At 2006/04/30 11:15 PM, Nick wrote:
--
[ Picked text/plain from
Well if you set the compiler options correctly, the code won't even compile
when you access a variable without initializing it. Unfortunately Valve's SDK
still needs a lot of work to be at that level. (I posted some of the changes
on the KI list.)
At 2006/04/27 03:57 AM, Garry Newman wrote:
--
[ Picked text/plain from multipart/alternative ]
which options? I tried to find those options in msvs2003 but i could not
find them
On 4/30/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Well if you set the compiler options correctly, the code won't even
compile when you access a variable
What defines that all variables are initialized to 0? Is it a compiler
flag, and why wouldn't you want this to be always set? This is the
first I've heard of it.
Ben Everett wrote:
The most common cause of crashes in release mode but not in debug are due to
variable initializations. In debug
--
[ Picked text/plain from multipart/alternative ]
It always seemed backwards to me.
When I'm in debug mode I want the compiler to do its best to try to make it
crash. I want it to throw a rain-man style spazz attack any time the
slightest thing is wrong.
I dunno though, I've kind of heard the
--
[ Picked text/plain from multipart/alternative ]
I think MSVC tries to be a little too freindly sometimes :) My C lecturer
had a laugh when I said that the compiler initilises everything to 0 :D Oh
well, in most cases that's not a bad thing to have, but it would promote
some bad habits if you
I just did a simple test and got the behaviour I just explained.
#include stdio.h
int main()
{
int *pValue;
printf(%p\n, pValue);
return 0;
}
VS.NET 7.1.3088 and VS8.0.50727.42
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
On 4/26/06, ChromeAngel [EMAIL PROTECTED] wrote:
Subject: Re: [hlcoders] Crash in release mode only AND Changing the
viewports
scheme
Reply-To: hlcoders@list.valvesoftware.com
ChromeAngel wrote:
2 Issues, I doubt they are related :
Issue 1) I've got my HL2DM mod running sweet
The most common cause of crashes in release mode but not in debug are due to
variable initializations. In debug mode all variables are initialized to
'0', while in release mode they do not have a default initialization value.
The most common cause of these crashes is failing to properly
2 Issues, I doubt they are related :
Issue 1) I've got my HL2DM mod running sweet and lovely and i'm about
ready to send it out to my testers, so I compiled in in release mode,
only to find it causes a crash in HL2.exe when I spawn on my listen
server. How should I go about finding the cause of
ChromeAngel wrote:
2 Issues, I doubt they are related :
Issue 1) I've got my HL2DM mod running sweet and lovely and i'm about
ready to send it out to my testers, so I compiled in in release mode,
only to find it causes a crash in HL2.exe when I spawn on my listen
server. How should I go about
11 matches
Mail list logo
