cobalt, in that example, blob is a constant.
changing the value of constants is not supported. that's what makes them constants. doing it anyway WILL result in 'undefined' behaviour. and by undefined, I mean 'predictable but horribly horribly buggy behaviour that can differ from one qcc to the next'.
DO NOT WRITE TO CONSTANTS.
add the var keyword if you want it to not be a constant.
any good qcc will warn about this.
compiling rogue devkit
Moderator: InsideQC Admins
13 posts
• Page 1 of 1
compiling rogue devkit
by Seven » Tue Aug 23, 2011 8:33 pm
- Seven
- Posts: 301
- Joined: Sat Oct 06, 2007 8:49 pm
- Location: Germany
Re: compiling rogue devkit
by Cobalt » Sat Aug 02, 2014 5:55 pm
-
Cobalt - Posts: 445
- Joined: Wed Jun 10, 2009 2:58 am
- Location: New England, USA
Re: compiling rogue devkit
by Spike » Sat Aug 02, 2014 6:09 pm
yes, it should be an error rather than a warning.
but then nothing would compile any more because QC coders are morons that give up as soon as they get the first error.
#pragma warning error Q106
should turn such warnings into errors.
but then nothing would compile any more because QC coders are morons that give up as soon as they get the first error.
#pragma warning error Q106
should turn such warnings into errors.
.
- Spike
- Posts: 2914
- Joined: Fri Nov 05, 2004 3:12 am
- Location: UK
Re: compiling rogue devkit
by Cobalt » Sat Aug 02, 2014 6:38 pm
-
Cobalt - Posts: 445
- Joined: Wed Jun 10, 2009 2:58 am
- Location: New England, USA
13 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest