For most functions the warning makes sense in strict mode. That's when
you should have a clean, finished function with the cruft removed.

The exceptions become painful though: callbacks and #ifdefs. And
sometimes when you develop in strict mode, because you will have
unused arguments while fiddling with things.

Plus deprecated arguments in APIs, but the compiler already have the
deprecate flag to hang that on.
      • Unused vari... Marcus Agehall (Roxen IS) @ Pike (-) developers forum
        • Unused ... Peter Bortas @ Pike developers forum
          • Unu... Per Hedbor () @ Pike (-) developers forum
            • ... Peter Bortas @ Pike developers forum
              • ... Per Hedbor () @ Pike (-) developers forum
              • ... Peter Bortas @ Pike developers forum
        • Unused ... Martin Stjernholm, Roxen IS @ Pike developers forum
          • Re:... Stephen R. van den Berg
            • ... Martin Stjernholm, Roxen IS @ Pike developers forum
            • ... Mirar @ Pike developers forum
              • ... Peter Bortas @ Pike developers forum
              • ... Per Hedbor () @ Pike (-) developers forum
              • ... Peter Bortas @ Pike developers forum
              • ... Mirar @ Pike developers forum
  • Re: Unused variables Mirar @ Pike developers forum
    • Re: Unused vari... Peter Bortas @ Pike developers forum
      • Re: Unused ... Per Hedbor () @ Pike (-) developers forum
        • Re: Unu... Peter Bortas @ Pike developers forum
          • Re:... Martin Stjernholm, Roxen IS @ Pike developers forum
            • ... Peter Bortas @ Pike developers forum
            • ... H. William Welliver III

Reply via email to