Useless ChangeLog entries

Richard Kenner kenner@vlsi1.ultra.nyu.edu
Mon Mar 6 11:39:00 GMT 2000


    Generally, the technical bits about why something changed belong as
    comments in the code.

I concur.

And I also note that those comments should be "time-independent" and
say why things are the way they are and not, in general, a history of
all the code that was ever at that location.  The latter type of comments
take a lot of time to read and usually confuse more than clarify.


More information about the Gcc mailing list