Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know that they provide a quick reference, but as the code grows they can lead to hundreds of files changing just due to version/history updates.
This leads/relates to my other question:
Is there a way to prevent code comments to be marked as changes in the diffs obtained from version control? (CVS/SVN)
Keep the version/history info in the version control. That’s what it’s good at.
Version/history info in the source file is only useful for people that read the source code without having access to your version control repository. How likely and how important is that scenario, to justify the effort you will require from your team to maintain these notes? My personal opinion is that this would add a lot of additional work for fringe benefits.