Legacy code - when to move on
Posted
by Mmarquee
on Stack Overflow
See other posts from Stack Overflow
or by Mmarquee
Published on 2010-03-21T01:34:37Z
Indexed on
2010/03/21
1:41 UTC
Read the original article
Hit count: 368
best-practices
|legacy
My team and support a large number of legacy applications all of which are currently functional but problematic to support and maintain. They all depend on code that the compiler manufacture has officially no support for.
So the question is should we leave the code as is, and risk a new compiler breaking our code, or should we bite the bullet and update all the code?
© Stack Overflow or respective owner