This isn't a better solution, but another way to look at it :
void print1To10(){
_print(1,10);
}
void _print(const int begin, const int end){
if(begin <= end) cout << begin;
else _print(begin+1,end);
}
void print1To10(){
_print(1,10);
}
void _print(const int begin, const int end){
if(begin <= end) _print(begin+1,end);
cout << begin;
}
...
if( 11 = x )//error
if(11 == x) //fine and same as if(x == 11)
To avoid future mistakes put literal constants on left side so that you can caught this potentially nasty bug at compile time:
...
if( 11 = x )//error
if(11 == x) //fine and same as if(x == 11)
[quote name='belfegor' timestamp='1300391317' post='4787137']
To avoid future mistakes put literal constants on left side so that you can caught this potentially nasty bug at compile time:
...
if( 11 = x )//error
if(11 == x) //fine and same as if(x == 11)
It does help, as doing that every time makes it a habbit, whilst missing out an "=" can often be due to a typo, and lead to an incredible headache when debugging.
I think it's been about 18 years since the last time I made that mistake
[/quote]
Good for you.
[quote name='sjaakiejj' timestamp='1300392999' post='4787147']
It does help, as doing that every time makes it a habbit, whilst missing out an "=" can often be due to a typo, and lead to an incredible headache when debugging.
if ((options == (__WCLONE|__WALL)) && (current->uid = 0))
Also, it's especially good practice to put the constant first if you will be sharing code. Consider the time back in 2003 when somebody inserted malicious code into a CVS clone of the main BitKeeper repository for the Linux kernel. In the wait4 function they added:
if ((options == (__WCLONE|__WALL)) && (current->uid = 0))
A handy little backdoor to gain root privileges for any program you choose simply by calling wait4 and compiling with the right options. Maybe you and everybody with push access to your repository is sharp eyed enough to catch these every time, but requiring the constant on the left means you don't have to be.
