OO
abbr. 面向对象程式设计(Object Oriented);已订购而尚未交货的(on order)
2026-04-13 21:58 浏览次数 19
abbr. 面向对象程式设计(Object Oriented);已订购而尚未交货的(on order)
1. the 15th letter of the English alphabet
2. a graphic representation of this letter
3. a speech counterpart of orthographic o
4. a graphic device for reproducing the letter o
5. one designated o especially as the 15th in order or class
6. something shaped like the letter O especially zero
7. ocean
8. ohm
9. old
10. order
11. over
12. the one of the four ABO blood groups characterized by the absence of antigens designated by the letters A and B and by the presence of antibodies against these antigens
13. offense
14. Ohio
15. pint
16. oxygen
17. egg
oology specifically ovum
oogonium
18. orth- or ortho-
19. one that is, has the qualities of, or is associated with
bucko
20. the number zero
21. zero sense 1
22. orth-; ortho-
23. the one of the four ABO blood groups characterized by the absence of antigens designated by the letters A and B and by the presence of antibodies against these antigens
24. opening
25. pint —used in writing prescriptions
OO of面向对象
oo brooch胸针
OO approach来代替面向对象的方法
OO Defrag磁盘碎片优化工具
OO UnErase恢复已删除文件
SHORE OO肖氏硬度
Oo Trance迷幻之夜
This allows for an elegant, easy to maintain, OO architecture that is pretty transparent, where you have real typed objects that travel seamlessly between the front and the back-end.
这考虑到一个优雅的、易于维护的、相当透明的OO架构,在这里你拥有真实类型的、无缝游历与前台和后天之间的对象。
They give you a firm foundation upon which you can add more OO habits and build software that is easily maintained and extended.
它们将为您提供更牢固的基础,在此基础之上建立更多OO习惯并构建可轻松维护与扩展的软件。
So why not give an entity all behavioral and state responsibilities, thus including the responsibility to perform persistence operations, as advocated by OO purists?
为什么不把所有的行为性和状态性职责都赋给实体呢,就像OO纯粹主义者所倡导的那样,让实体自己负责持久化操作。
Most of the traditional OO systems and programs consist of business objects manipulating hierarchies of domain data objects.
大部分传统OO系统和程序都包括对领域数据对象的层次结构进行操作的业务对象。
Tenet 3: Services share schema and contract, not class So do all of my OO programs with interface and classes.
信条3:服务共享数据定义与契约,而非类。我所有的采用接口与类的OO程序都满足这条。
Remember that the reason for adopting OO habits is to carefully encapsulate change so your code is more extensible and maintainable.
记住采用OO习惯的原因是要谨慎封装更改,这样代码将更具有可扩展性并且更容易维护。
When used in the absence of an up-front OO design, nothing creates more havoc than copying code from one file to the next.
当在缺少预先OO设计的情况下使用时,没有任何操作会像在类之间复制代码那样具有破坏性。
On the design level, the goal of OO is to enable rapid and efficient design, development, and execution of applications that are flexible and extensible.
在设计层,OO的目标是能够进行快速而有效的设计、开发以及执行灵活且可扩展的应用程序。
See Resources for more on this way of looking at OO systems.
有关以这种方式考虑OO系统的更多信息,请参阅参考资料。
However, OO still is a valuable approach for design of the underlying class and component structure within a defined service.
然而,对于设计已定义的服务中的底层类和组件结构,OO仍然是一种有价值的方法。
For more information about the benefits of OO design that are language-independent, see Resources.
有关独立于语言的OO设计优点的更多信息,请参阅参考资料。
OO development focuses on incremental development of applications, implementing one business scenario or use case at a time.
OO开发集中于应用程序的渐进式开发,每次实现一个业务场景或用况。
OO is a well-established paradigm familiar to the majority of developers.
OO是被大多数开发者所熟悉的行之有效的范式。
For example, applying general software architecture principles and OO techniques is a valid start in any SOA effort.
例如,在任何SOA工作中,应用通用的软件体系结构原则和OO技术都是一个有效的开端。
If you constructed Work Order as an OO application, these software objects would contain all the necessary business rules and would understand the business processes that should be followed.
如果您将工作订单构造为一个OO应用程序,这些软件对象将包含所有必需的业务规则,并且理解应该遵循的业务流程。
Anyone familiar with OO design principles knows that these questions have been answered long ago through the creation and application of design patterns.
熟悉OO设计原则的人都知道,很久以前就通过设计模式的创建与应用对这些问题进行了处理。
The OO literature spends virtually all its time discussing the objects and its interactions with other objects as in-memory objects.
实际上,OO文献整个都在讨论对象,以及它作为内存中的对象与其他对象的交互。
These types of inheritance are very common in OO analysis, design, and programming.
这些类型的继承在OO分析、设计和编程中极为普遍。
To understand the benefits, let's consider some things that we can express in requirements but not implement directly in pure OO code.
为了理解这些好处,让我们考虑一些我们可以在需求中表达但无法直接用纯oo代码实现的情况。
A crosscutting concern, when implemented in a traditional OO approach, cuts across many classes and methods.
一个横切关注点,在用传统OO方法实现时,会分解成很多类和方法。
This does not exclude the OO viewpoint adopted by RUP, but rather implements another layer of abstraction above it.
这并没有排除RUP采用的OO观点,而是在其上实现了另一个抽象层。
aught任何事物(等于 anything);无,零;无价值之物
cipher使用密码;计算;做算术
goose egg零分;青肿块;鹅蛋
nil(Nil)人名;(阿拉伯、土、土库、阿塞、哈萨、塔吉、吉尔、乌兹、匈)尼尔;(柬)尼
nothing无;零;无关紧要的事
oh哦;哎呀(表示惊讶或恐惧等)
zero零
zilch(Zilch)人名;(德)齐尔希
zip给...以速度;拉上或拉开拉链