Earlier, I showed composition as a code-reuse mechanism.
在以前的文章中，我展示了通过复合实现的代码重用机制。
Code reuse is an obvious development goal, and imperative abstractions tend to solve that problem differently from the way that functional programmers solve it.
代码重用是一个显著的开发目标，而命令式抽象倾向于用不同于函数式程序员解决问题的方法来解决问题。
Such functions encourage code reuse and simplify the development and maintenance of queries.
这些函数有助于促进代码重用，简化查询的开发和维护。
Because both of these problems rely on a number's factors, they are good candidates for refactoring (no pun intended) and thus for illustrating styles of code reuse.
由于这两个问题都依赖于数字因子，它们都是重构(不是双关语)和说明代码重用风格的最佳候选者。
Code reuse also illustrates the difficulties of IT governance.
代码重用也体现了IT治理的难点所在。
This code reuse meant that users could expect more consistent behavior.
该代码重用意味着用户期望更加一致的行为。
Callbacks are implemented as real classes to help facilitate code reuse and associated with client data at run time.
将回调实现为真正的类，从而促进代码重用并允许在运行时与客户机数据关联。
Templating — The ability to create a template for page code reuse and substitution.
模板化 ——能够创建用于页面代码重用和取代的模板。
Rather, I did it by using composition rather than coupling for code reuse.
相反，我是通过使用组合而非耦合来实现代码重用。
The benefits of doing so include flexibility, keeping maintenance of the application easy as it grows, code reuse, and better performance.
这么做的好处包括灵活性、保持应用程序易于维护、代码重用和更好的性能。
However, code reuse across process boundaries has been much more problematic.
然而，跨过程边界的代码重用有更多的问题。
Software developers have always pursued code reuse — and for obvious reasons.
软件开发人员一直在追求代码重用——原因很明显。
The distributed objects approach focuses on code reuse and language independence, while asynchronous messaging addresses the problem of tight coupling between applications.
分布式对象方法侧重于代码重用和语言独立性，而异步消息传递则解决了应用程序之间紧密耦合的问题。
As always, code reuse is definitely a good thing.
象往常一样，代码重用无疑是个好东西。
Applying the concepts in Part 1 can open new opportunities for code reuse.
通过应用第1部分中的概念，可以提供新的代码重用机会。
In addition to promoting code reuse, it can also break complex transforms into chunks that are easy to understand.
除了促进代码重用，它还可以将复杂的转换分成易于理解的程序块。
Object oriented technologies introduced significant improvements for code reuse within an application.
面向对象技术的引入显著地改善了应用内部的代码重用。
For this and the next installment, I tackle code reuse via refactoring and the attendant abstraction impact.
为此，在本文与此后的文章，我将通过重构以及随之而来的抽象影响来处理代码重用问题。
To illustrate code reuse and its implications, I return to a version of the number classifier that previous installments use to illustrate code structure and style.
要说明代码重用及其含义，我要回过来谈谈先前文章说明代码结构和风格所用的数字分类器。
The fact that the API remains common across message types encourages code reuse even in environments where the message types are completely different.
此api可以对多种消息类型进行公共访问这一事实可促进代码重用，即使在消息类型完全不同的环境中也是如此。
By adding clean syntax and support, functional languages make recursion a candidate for simple code reuse.
通过增加简明的语法和支持，函数式语言使递归成为实现简单代码重用的候选方法。
Control flows help promote code reuse, and they enable developers to specify the sequence of various activities.
控制流有助于促进代码重用，还让开发人员能够指定活动的次序。
The latter technique is useful for complex operations and helps promote code reuse.
后一种技巧对于复杂的操作比较有用，并且可以促进代码重用。
The goal here is largely to enable meaningful code reuse: Each path component causes dispatch to a relevant code handler.
这样做的主要目的是支持有意义的代码重用：每个路径成分委派给一个相关的代码处理器。
Service proliferation, in turn, results in service governance problems, making it harder to pursue effective code reuse.
服务大量增加反过来会导致服务治理问题，从而使得更难获得有效的代码重用。
Unfortunately, tossing out private and multiple inheritance has cost us dearly in terms of code reuse.
遗憾的是，彻底放弃私有继承和多重继承会使我们在代码重用方面付出昂贵的代价。
In each case, the solution is succinct and declarative. This illustrates code reuse by composing parameters and functionality to create generic behavior.
每一个例子中的解决方案都即简单又具有很强的说明性，通过组合参数和功能来创建通用行为，进而阐述代码重用。
Make code reuse easier because of a consistent API.
使代码重用更容易，因为有一个统一的API。
This series of articles demonstrates what a powerful code reuse mechanism DI is.
本系列演示了DI是多么强大的代码重用机制。
SOA reusability goes far beyond traditional code reuse.
SOA的重用不仅仅是传统的代码重用。
应用推荐