依据可复用类建立过程中所遵循的复用原则、分类原则、标准化原则，给出了可复用类的基本模型和建立方法。
According to reuse principles, classify principles, standardization principles in the course of establishing the reusable class, a model of reusable class and methods of establishment are given.
如果您遇到根据逐类原则调整WebLogic缓存大小的应用程序，则在调整WebSphereEJB缓存大小时应该将这些缓存大小考虑在内。
If you encounter an application where there has been tuning of the WebLogic cache sizes on a class-by-class basis, you should consider those cache sizes in tuning the WebSphere EJB cache size.
也许有一些关乎生死或最高原则的事情可以证明这种冒险是合情合理的，但属于这一类别的事情并不多。
There may be some matters of life and death or highest principle, which might justify such a risk, but there aren't many things that fall in this category.
测试驱动的开发的总体原则之一就是应测试一个类已发布的所有接口。
A general principle of test-driven development is that you should test all published interfaces to a class.
在遵循开闭原则的过程中，我期望能够写出一个类或者方法，在以后我回过头读它的时候，会很舒服地看到它能完成它的工作并且我也不需要再修改它。
In following the Open Closed Principle, I want to be able to write a class or a method and then turn my back on it, comfortable that it does its job and I won't have to go back and change it.
如果我前面所说的，使用开闭原则最通常的做法就是使用多态去用一个全新的类替换程序中现存的一部分。
As I said earlier, the most common manifestation of the Open Closed Principle is using polymorphism to substitute an existing part of the application with a brand new class.
单一责任原则的要点不仅仅是写一些更小的类和方法。
The point of the Single Responsibility Principle isn't just to write smaller classes and methods.
还假定读者了解在php中的类与对象的相关知识，因为文中所采用的PHP组件是遵照OOP原则来编写的。
I also assume that you know the basics of working with classes and objects in PHP, as the PHP components used in this article are written in compliance with OOP principles.
你永远也达不到真正的开闭天堂，但是通过严格地遵循与之相关的单一责任原则：一个类应该有并且只有一个更改的理由，你可以非常靠近地接近它。
You'll never reach true Open Closed nirvana, but you can inch much closer by rigorously following the related Single Responsibility Principle: a class should have one, and only one, reason to change
可能这就是ducktyping的一个例子，duck typing所代表的原则是，无论对象属于什么类或者模块，关系都不大，关键在于它做些什么。
Perhaps it's a case for duck typing, the principle that it doesn't really matter what an object is, in terms of class and module, but only what it does.
违反开发闭合原则的类结构。
违反Liskov替换原则类结构图。
我使用了六个通用原则来指导simplelinearregression类的开发。
I used six general principles to guide the development of the SimpleLinearRegression class.
这个原则指出，如果有两个原因去修改一个类，我们必须拆分它的功能到两个类中。
This principle states that if we have 2 reasons to change for a class, we have to split the functionality in two classes.
清单1用两个类：KerberosTGT和KerberosSecretKey的定义说明了这些原则。
Listing 1 illustrates these principles with the definition of two classes: KerberosTGT and KerberosSecretKey.
如果你可以通过实现IDataSource对这个系统进行扩展并且不对BusinessProcess类做任何的修改，那么这个设计就遵循了开闭原则。
The design follows the Open Closed Principle if you can extend the system by swapping out implementations of IDataSource without making any change to the BusinessProcess class.
RestTemplate执行RESTful原则，是客户端HTTP访问的中心类。
RestTemplate implements RESTful principles and is the central class for client-side HTTP access.
当提及类的打开关闭原则，它可以通过抽象类和实体类实现行为的方式来确保。
When referring to the classes Open Close Principle can be ensured by use of Abstract classes and concrete classes for implementing their behavior.
同样的原则可以被应用在模块、包、类库上。
The same principle can be applied for modules, packages, libraries.
遵循单一责任原则的最简单办法就是不断地问自己是不是这个类的每一个方法和操作都与这个类的名称直接相关。
An easy way to follow the Single Responsibility Principle is to constantly ask yourself whether every method and operation of a class is directly related to the name of that class.
依赖倒置原则声明了我们应该将高层模块和低层模块解偶，在高层类和低层类之间引入一个抽象层。
Dependency Inversion Principle states that we should decouple high level modules from low level modules, introducing an abstraction layer between the high level classes and low level classes.
如果在某一部分中，一个抽象了的类必须向下转换为特定的子类，那么你就没有遵循开闭原则。
If a class that uses an abstraction has to downcast to a specific subclass in one section, you're not following the Open Closed Principle.
原则上，此技巧也适用于老式类，并且应该容易编写一个实现来使老式类保持老的样式。
In principle, the trick also works for old style classes, and it would be easy to write an implementation keeping old style classes old style.
记住这个原则：“使主程序尽量简单，而将复杂的业务作为类放到库中”。它将帮助你解决测试GUI应用程序的问题。
The idea of keeping the main program very simple and putting the business complexity into classes contained in a library can also help solve the problem of testing GUI applications.
不幸的是，它同时也意味着该属性也能够被相同包下面的其他的类直接访问，这违反了标准的面向对象的使所有属性私有的原则。
Unfortunately this means the fields can be accessed directly by other classes in the same package, so you shouldn't use this in public API.
这和设计方法和类的原则类似。
This is similar to the principle for designing methods and classes.
这意味着在CSS中我们的一个类应该有一个原则而且只有一个理由去改变。
The principle implies that A class should have one, and only one, reason to change. In CSS we have.
这个原则意味着复杂的对象应该由更小的对象组合起来比用从比较大的类中继承这种行为更好。
This principle implies that complex objects should be composed from much smaller, rather than inheriting behaviour from a much larger, monolithic object.
让我们从讨论一些通用的原则开始，这些原则指导我开发这个simplelinearregression类。
Let's begin by discussing some general principles that guided my development of this SimpleLinearRegression class.
让我们从讨论一些通用的原则开始，这些原则指导我开发这个simplelinearregression类。
Let's begin by discussing some general principles that guided my development of this SimpleLinearRegression class.
应用推荐