On Sat, Aug 2, 2008 at 11:41 AM, Robert Bradshaw
<[EMAIL PROTECTED]> wrote:
> Is there anything we could do to suppress this warning (fool the
> compiler into thinking it's used, but still have it be optimized away)?
Assigning the variable to itself worked in the following test:
void foo(char *x) {
x = x;
}
You can also suppress the warning with a gcc attribute, but that's
compiler-specific, so you'd have to guard it with ifdefs etc.
Carl
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
