At 10:32 -0700 27/9/04, Scott Moore wrote:
Procedures and functions with unused parameters appear in good code all the time. You build programs by constructing outlines with the routines stubbed out, simply serving as placeholders for routes yet to be constructed. At some point, the program is even going to become operational with many of the unfinished routines left stubbed out. This is a good, organized design method, and its to be encouraged. To me, it means the programmer plans ahead.
Yes, I agree entirely, and it is a good argument for the need to be able to explicitly mark parameters that are unused. Not for the functions you describe, but for everywhere else they might happen so that the warnings for the functions you describe appear cleanly to remind the programmer of what is still unfinished, without being buried by lots of spurious warnings for callback functions and such that will never use the extra parameters. Peter.