Darwin g++ build broken

Darwin g++ build broken

(I just fixed it in 6bfae95.)

This makes me ask:  Is it really worth optimising the code for warn-
ings to this extent?  Would it not be better to silence warnings spe-
cific to gcc-on-Linux that are spurious, instead of trying to work
around them?

We seem to be optimising for warnings over and above maintainability
now.  This type of code, for example, is harder to fathom for the cas-
ual reader than the shorthand equivalent:

int foo;
foo = ...;
PERL_UNUSED_ARG(foo);

• Darwin g++ build broken by Father Chrysostomos
• Re: Darwin g++ build broken by Dave Mitchell