For any two classes that have some relationship, identify the semantics of the relationship: is it association, aggregation, composition, or inheritance?
对于任意两个之间具有关系的类，确定关系的语义：是关联、聚合、合成还是继承？
There are four types of relationships that an object can be involved with: inheritance, association, aggregation, and composition.
对象之间有四种类型的关系：继承、关联、聚合和组成。
It is my prototypical example for the flexibility of composition over inheritance.
这是我用以说明组合的灵活性要比继承好的最佳样板。
We find object inheritance hierarchies and object composition hierarchies.
我们可以看到对象继承层次结构和对象组合层次结构。
The better alternative USES composition rather than inheritance, as illustrated in Figure 3.
较好的替代方案就是采用组合而不是继承，如图3所示。
We also see that all these objects can contain a number of TAG/DataElements since this composition is represented at the parent of the object inheritance hierarchy (DICOMData).
我们还看到所有这些对象都可以包含多个TAG/DataElement，因为该组合是在对象继承层次结构的父类（DICOMData）中表示的。
In the article Bejeck is trying to create components with a mixture of inheritance and composition, and enforce separation of concerns, especially between view and business logic.
Bejeck在文章中试图创建混合了继承和组合关系的组件，实施分离关注点，尤其是分离视图和商业逻辑。
Go encourages the use of composition and delegation over inheritance, and offers some syntactic sugar to make it more bearable.
相较于继承，Go鼓励使用组合和委派，并为此提供了相应的语法甜点使其更容易接受。
You can think of this as externalizing composition, which accounts for a much larger proportion of code than inheritance in a typical application.
可以将它看成具体化复合（externalizing composition），在典型应用程序中，它的比重远远大于继承。
I find myself agreeing with Ashraf in his advocation of using basic oo design principles (encapsulation, loose coupling, favour composition over inheritance etc) concepts in applying these to SOA.
我比较赞同ashraf的观点——将OO的设计原则(封装、松耦合、重组合轻继承)应用于SOA。
Class abstractions are extended by subclassing and a flexible mixin-based composition mechanism as a clean replacement for multiple inheritance.
Class的抽象可由子类化和一种灵活的基于mixin的组合机制(它可作为多重继承的简单替代方案)来扩展。
A common misunderstanding is that composition doesn't use inheritance at all.
一个常见的误解是组合完全不会使用到继承。
Either inheritance or composition offers a cleaner way to extend the framework, and it's an even bigger indictment if those are both impossible.
继承或复合都提供了一种更加干净的方法来扩展框架，如果这两种方法都不可行的话，那么问题就更加严重了。
Most of them use composition with interface inheritance.
这些都使用了通过实现接口来使用组合。
In order to make styles clean and predictable we need to use composition rather than inheritance.
为了使样式更干净而且更有可预测性，我们要多使用组合而不是继承。
Owing to the metallogenetic inheritance of placer gold and mountain gold, their liquid-inclusion composition are very similar.
由于成矿作用的继承性、砂金的气液包体成分同原生的金十分相似。
In the author's composition of the image of snow, we could also detect an inheritance from Chinese literary tradition of the song of snow.
在雪意象的营构过程中，我们还可以窥见曹雪芹对中国传统咏雪文化的继承。
Favor composition over inheritance.
优先使用组合，而不是继承。
Favor object composition over class inheritance.
优先使用对象组合，而非继承。
Chapter 8, composition, discusses and demonstrates some practical examples of composition, as well as program examples that combine composition and inheritance.
第8章，合成。讨论并演示一些合成的实例，以及组合合成与继承的程序示例。
Chapter 8, composition, discusses and demonstrates some practical examples of composition, as well as program examples that combine composition and inheritance.
第8章，合成。讨论并演示一些合成的实例，以及组合合成与继承的程序示例。
应用推荐