legacy code造句

Even if you have a large, untested legacy code base, start writing tests for it now.

For a variety of reasons — legacy code, manpower, budget, priorities — some consumers may not migrate in a timely fashion.

It also provided a layer of protection between new and legacy code, ensuring the two types of code did not inappropriately affect one another.

Disabling these options on legacy code can be risky, however, since they may be depending upon them being set for proper execution.

If you don't already have 10 years of legacy code that reads, writes, and displays something close to this, you have no hope of implementing it.

One problem you're likely to encounter in test-last as opposed to test-first development, especially with legacy code, is that there are often unadvertised dependencies and prerequisites.

You can even mix approaches if you wish, allowing legacy code to specify EJBs using descriptors while new EJBs are declared with annotations.

You should consider either refactoring your legacy code to ensure that interfaces are strongly typed or building a mediation that will wrapper the weakly typed interface with a strongly typed one.