|Do you know where your variables are?|
if there's a way to tell gcc to compile "0U-300U" into something that ends up being effectively -300 in the object code.
Eeek! Subtracting an unsigned integer from unsigned zero to derive an negative (signed) integer is just weird!
#define HDN_FIRST -300 #define HDN_BEGINTRACK (HDN_FIRST-26) into Header.xs and live with the compiler warnings. But that's just ugly.
If that works and the only concern is the compiler noise, perhaps you can shut them up by preceding your #defines with:
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.