Revision as of 17:49, 11 December 2020 edit Pelirodri1248 (talk \| contribs) Extended confirmed users 805 edits m →Legacy problems ← Previous edit		Revision as of 17:49, 11 December 2020 edit undo Pelirodri1248 (talk \| contribs) Extended confirmed users 805 edits m →Legacy problems Next edit →
Line 122: '''Example 2''': legacy code may have been compiled and tested on 32-bit architectures, but when compiled on 64-bit architectures, new arithmetic problems may occur (e.g., invalid signedness tests, invalid type casts, etc.). '''Example 3''': legacy code may have been targeted for offline machines, but becomes vulnerable once network connectivity is added. * Legacy code is not written with new problems in mind. For example, source code written ~~about~~in 1990 is likely to be prone to many [[code injection]] vulnerabilities, because most such problems were not widely understood at that time. Notable examples of the legacy problem:

Defensive programming: Difference between revisions