You can keep the code object oriented by encapsulating the actual model knowledge within the model itself.
您可以通过将实际的模型知识封装到模型中来保证代码是面向对象的。
Object oriented technologies introduced significant improvements for code reuse within an application.
面向对象技术的引入显著地改善了应用内部的代码重用。
Object oriented design questions are very important, as they demonstrate the quality of a candidate's code a poor performance on this type of question raises serious red flags.
面向对象设计的问题非常重要，它能反映出面试者的代码质量。若是对此类问题支支吾吾，面试多半就凶多吉少了。
AOP or Aspect Oriented Programming allows developers to "weave" code fragments through their object and methods without explicitly placing the code in the class's source.
AOP或者说面向方面编程支持开发人员将代码段“织入”到对象和方法中，而不需要显式地将代码放入到类的源代码中。
Closures can integrate just as well with object-oriented code, as well as with procedural code.
闭包可以很好地与面向对象的代码以及面向过程的代码整合。
In general, code with aspects performs similarly to that of a purely object-oriented solution, where the crosscutting code is scattered throughout the system.
一般来说，使用方面的代码执行起来与纯粹面向对象的解决方案类似(这类方案中横切代码散落在整个系统中)。
In looking at the object-oriented version of the code, you can see that the code becomes more abstract.
查看该代码的面向对象版本，可以看到代码变得更加抽象。
To reuse object-oriented code, you extract the target code into another class, then use inheritance to access it.
要重用面向对象的代码，您要将目标代码提取（extract）到另一个类中，然后再用继承来访问它。
If you spend much time with Jena, you'll begin to realize that a gap exists between what's considered to be normal object-oriented code and your client code that interacts with the Jena API.
如果花大量时间研究Jena，您将会认识到普通的面向对象代码和与Jena API交互的客户端代码之间存在差异。
Objects and closures get along very well, as we saw by the special handling of closures within object-oriented code.
对象与闭包可以很好地结合使用，比如我们在面向对象的代码内对闭包的特殊处理。
Design principles: Validates that your code adheres to the design principles of object-oriented programming.
设计原则：验证你的代码是否坚持面向对象编程的设计原则。
However, when you end up refactoring a large code base, coupling pops up everywhere because that's one of the reuse mechanisms in object-oriented languages.
然而，当您重构大型的代码库后，到处都会出现耦合的地方，因为那是面向对象语言中的其中一种重用机制。
Clearly, the boilerplate portion of this code could be reused, and we typically do so in object-oriented languages by creating structure.
很显然，该代码的样板文件可重复使用，我们通常会在面向对象语言中通过创建架构来实现。
This is the beauty of object-oriented design; it allows experienced developers to constantly reuse code they have written, and save themselves quite a bit of time.
这是面向对象的设计的美妙之处；它允许有经验的开发人员不断重用已编写的代码，从而节省大量的时间。
On the other hand, object-oriented programming can be a very useful way to create abstraction, and thus resuable code.
另一方面，对于创建抽象从而创建可重用的代码来说，面向对象的编程可能是非常有用的方法。
Even if you decide to stay away from object-oriented programming in your own code, you will likely need to know object-oriented programming.
但即使您决定在自己的代码中不使用面向对象的编程，您仍可能需要了解面向对象的编程。
His code is messy because he does not follow best practices and never makes use of object-oriented programming (OOP).
因为从不进行实践检验，和应用面向对象程序设计(OOP)，他的编程都混乱不堪。
As a result, developers often find their code departing from the object-oriented model and diving instead into a procedural programming style.
因此，开发人员常常发现他们的代码偏离了面向对象模型的轨道，反而陷入了过程编程模型的泥潭。
The new object-oriented features and the addition of exception handling provide compelling reasons for migrating your code from PHP V4 to V5.
新的面向对象特性和异常处理的增加为将代码从PHPV 4迁移到PHP V5提供了强有力的理由。
It is common in object-oriented development to abstract out a common interface that may have multiple implementations and write code that works with the interface, making it more reusable.
在面向对象的开发中，有一种实践很常见：抽象出一个可能拥有多个实现的接口并编写代码以使用该接口，从而使其可以重复利用。
Remember: If you're using PHP V5 or later, you can incorporate object-oriented concepts to make your code easier to read and maintain.
记住：若使用的是PHPV 5或更新的版本，就可以融入面向对象的概念以使代码更易于读懂和维护。
Also the object-oriented architecture makes the code structured, reusable, and fast.
而且，面向对象的体系结构使代码结构化、可重用并且运行快速。
Take a tour through some of PHP's new object-oriented features and learn how to migrate existing PHP V4 code into V5.
让我们来看一些php新的面向对象特性，并了解如何将现有PHPV 4代码迁移到PHP V5。
Writing aspects to be testable yields design benefits parallel to those achieved by factoring object-oriented code for testability.
将方面编写为可测试的，得到的设计好处与通过重构面向对象的代码来实现可测试性所得到的好处相似。
Which means you have all learned about good code, object-oriented design, style, good practices, and so on, and refactoring is just another buzzword that someone invented to sell some books.
这意味着你对于如下种种早已熟谙于心：编写好的代码，面向对象设计，编码风格，最佳实践，如此等等，不一而足。重构无非是某些人的故作玄虚之语，编造出来用以兜售自己的新书，如此而已。
As implemented in traditional object-oriented programming, these concerns are handled as individual instances, introducing potentially unrelated code (that is, clutter) into application classes.
就像在传统面向对象编程中实现的那样，这些关注点是作为单独的实例处理的，有可能在应用程序类中产生互不相关的代码(就是混乱)。
Code written in these languages require type annotations less often than in Scala, because Scala's type inference algorithm has to support object-oriented typing as well as functional typing.
用这些语言写出的代码需要比Scala更少的类型注解，因为Scala的类型推断算法得同时支持面向对象类型和函数式类型。
The main aim of this article is to introduce people who are used to scripting procedural code in Bash, PHP, or some other language, and to assist them in moving into object-oriented Python developing.
本文的主要目标是向习惯于使用Bash、PHP或其它某种语言编写脚本过程代码的人介绍面向对象的Python 开发，并帮助他们转换到面向对象的 Python 开发。
This article was somewhat experimental, as it went from Bash and PHP, to procedural, object-oriented, and finally functional Python using the same basic code.
本文有点试验性质，因为它从Bash和PHP谈到了过程、面向对象，并在最后谈到了使用相同基本代码的函数式python。
This article was somewhat experimental, as it went from Bash and PHP, to procedural, object-oriented, and finally functional Python using the same basic code.
本文有点试验性质，因为它从Bash和PHP谈到了过程、面向对象，并在最后谈到了使用相同基本代码的函数式python。
应用推荐