http://ideone.com/lrUb9U

#include <stdio.h>
 
#define BLA 8
 
int main(void)
{
    int a, b;
    int s = BLA;
    unsigned char data[1] = {0};
 
    a = (data[0] < (unsigned char)(1 << s));
    b = (data[0] < (unsigned char)(1 << BLA ));
 
    printf("%d %d\n", a, b);
}

Heh, heh.

yet another Brain Fart that boggled me for a few minutes.
And no compiler to the rescue this time.

if ( !oldPath || oldPath[O] == '\0') {
        return bestOrder;
    }
}

I really need to go back to a qwerty keyboard when I code…

Not the compilers fault you define O as a numerical constant :)

Edit:
I'm just assuming you're still using ROM's bit system which defines O.

#define O			16384

If this weren't the case, you would certainly get a compiler error.

Yep that's the reason. Still having O and 0 so close on the keyboard is annoying as hell. And in azerty I need to hold shift to get the 0. At least in qwerty you don't have this problem as you will catch the size difference :o0