quote:Original post by TreborZehn
It''s also interesting to me that leaving a parameter unnamed doesn''t give the warning... not sure if I like that idea. I mean I''m not doubting that it works I''m just thinking if it''s a good thing from a Programming Practices perspecitive.
Suppose you''re implementing an interface defined by someone else. Then you might not want to utilize all parameters you get in a function call (while somone else, in another implementation of the same interface, could need all parameters). Therefore it''s really necessary not being forced to use all parameters, and it''s a really valid and useful thing to do. So not having a warning in that case is a good thing.
A static code analyzer, such as LINT, can probably be configured to issue warnings in this case.