tag:blogger.com,1999:blog-35928092.post7014789058428782665..comments2008-07-18T14:27:42.941-04:00Sargsyan Tigranhttp://www.blogger.com/profile/17269775074544232074noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-35928092.post-26924525719395385162008-07-18T14:27:00.000-04:002008-07-18T14:27:00.000-04:00That is so crazy, I still can't believe that. Whoever did that deserves a special place reserved for them in the customer support section :)Jason Mawdsleyhttp://www.blogger.com/profile/12753716679505402680noreply@blogger.comtag:blogger.com,1999:blog-35928092.post-459385328595323912008-07-18T08:32:00.000-04:002008-07-18T08:32:00.000-04:00Not that I want to one-up you on this but I have been doing work with a popular ASP.Net component library.<BR/><BR/>With that library, when you buy a certain level of license, you get the source. I looked in there and is was scary. They seem to be doing version control with #ifdef statements.<BR/><BR/>The code is littered with #if V3.2 type of statements. I wonder if they ever heard of branching?Francishttp://www.blogger.com/profile/11917210826902818268noreply@blogger.comtag:blogger.com,1999:blog-35928092.post-3689201827013135222008-07-18T01:01:00.000-04:002008-07-18T01:01:00.000-04:00I think placing comments about the deleted code in the commit logs or patch's change log is the best way to deal with this kind of problem. Sometimes it is also possible to write done little explanation comments in the code, but just commenting out the code which should be deleted is not a good practice.Sargsyan Tigranhttp://www.blogger.com/profile/17269775074544232074noreply@blogger.com