in reply to Re^2: How do I prototype a function with a varying number of arguments?
in thread How do I prototype a function with a varying number of arguments?

BrowserUK is strictly a minimalist (or perhaps a zeroist), and feels comments only get in the way, and I'm a semi-maximalist, who feels that comments should be there to clarify intent, point out pitfalls, and explain complex code to the reader.
I tend to be both. I feel comments should be there to clarify intent, etc. I also prefer to have as few comments as possible.

Impossible you say? I disagree. If your code is simple enough, there just isn't much reason to add a comment. If I feel the need to write a comment to explain my code - I also consider rewriting the code instead so the comment may no longer be needed.

  • Comment on Re^3: How do I prototype a function with a varying number of arguments?

Replies are listed 'Best First'.
Re^4: How do I prototype a function with a varying number of arguments?
by pemungkah (Priest) on Aug 08, 2011 at 17:47 UTC
    Completely agree on both these points. Sometimes you just have to explain what the heck is going on because there are reasons you had to do it that way (the kernel bug I reference in my post is an example).

    If it is possible to clarify to eliminate the need for the comment without sacrificing performance or correctness then I'm all for the code that doesn't need it.