That is a rather bold sentiment. At uni the attitude is opposite - I actually saw home assignments stating "remember to use many comments to make the code more readable". I actually agree with you; there is much less clutter if the comments don't duplicate that which is already communicated through good naming, and the code is more readable when good naming makes comments superfluous.
On Wed, 26 Dec 2018 at 21:57, Bobby Powers <bobbypow...@gmail.com> wrote: > > On Wed, Dec 26, 2018 at 10:44 AM <sylvain.bertr...@gmail.com> wrote: > > Preprocessor. I guess having 2 ways to define comments is not significant, > > then better stick to one and the historical one. > > Better than one way is zero ways -- comments are not semantically > significant, so rather than argue about which standards-defined > comment style to use it would better to ban them all. >
