You will be quizzed on chapter 6 tomorrow.
明天将考你们第6章。
One of the funniest episodes in the book occurs in Chapter 6.
书中最有趣的片段之一在第6章。
阅读第6章, 161kb,pdf.
In chapter 6 we have the Battle of Jericho.
第六章中有耶利亚哥战役。
Chapter 6 covers structures and unions.
第6章讨论结构和联合。
Chapter 6: Lean Software, DSDM, and FDD.
第6章精益软件、DSDM和fdd。
Chapter 6 digresses to talk about diagrams.
第6章讨论了有关图的内容。
Chapter 6: Full text summary and work outlook.
第6章：全文总结与工作展望。
Chapter 6: Working from Your Services to the clouds.
第六章：将服务移入云。
Chapter 6 illustrates the concepts of event driven programming.
第6章介绍了事件驱动的程序设计概念。
Sub-processes and event handling will be discussed in chapter 6.
子流程和事件处理将在第6章讨论。
The promises he's referring to are mentioned at the end of chapter 6, namely
他所指是在第六章结尾部分提到的应许，也就是
Chapter 6 Legal relations and application of QFII cross boarder holding.
第6章Q FII跨境持有的法律性质及适用。
If Chapter 4 was the Perl 6 driving manual, Chapter 6 is the engine parts list.
如果说第4章是Perl6的驾驶手册，第6章就是引擎部分列表。
Chapter 6 focuses on crafting input in general, and malicious input specifically.
第六章主要关注在通常的工艺输入上，并且特别是恶意的输入。
Most of the features shown in Chapter 4 are not in Chapter 6, but the means to achieve them are.
第6章中并没有展示第4章中的大部分特性，但是展示了其实现方法。
Chapter 6 is about infinite streams; I couldn't finish it, it just went on and on (okay, joking!).
第6章是有关无限数据流的问题；我们不能结束这个数据流，它只会无限制地继续下去(开玩笑)。
Today, we're going to cover Attraction (Chapter 6 from the book). The next email will be on Qualification.
今天我们讨论吸引力(《谜男》第6章)。下次我们将讨论筛选与合格的问题。
Observe the precautions involved in the use of desiccators mentioned in Chapter 6 of the Techniques Manual.
留意在第6章技术手册所提到的干燥器使用的注意事项。
This follows the "Fault Tolerant Hierarchy" approach described in chapter 6 of Software Architecture in Practice.
这遵循的是《SoftwareArchitectureInPractice》第6章中所述的“容错层次结构”方法。
Chapter 6, Rule 6: Put scripts at the Bottom shows how scripts affect rendering and downloading in the browser.
第6章，规则6——将脚本放在底部：展示了脚本是如何影响呈现的，以及脚本是如何下载到浏览器中的。
See Chapter 6 for a description of how these modifiers apply to classes; they have the same effect on delegates.
参见第6章如何把这些修饰符运用于类的描述，它们在委托上有同样的效果。
But from these two definitions appearing in book III chapter 6 and book IV chapter 1 we learn a number of important things.
但从这两个出现在，第，III，册第，6，章和第，IV，册第，1，章的定义1，我们得知一些重要的事。
We'll see how in the section called "Overriding Abstract Types" in Chapter 6, Advanced Object-Oriented Programming in Scala.
我们会在《第6章-Scala高级面向对象编程》中的“重写抽象类型”章节看到如何做到这一点。
We'll discuss overriding abstract and concrete members in detail in Chapter 6, Advanced Object-Oriented Programming in Scala.
我们会在《第6章-Scala高级面向对象编程》中详细讨论重写抽象和具体成员。
For example, the explanation of stacks and register frames in Chapter 6 connected with Chapter 4's explanation of variable scope.
例如，在第6章中对栈和寄存器结构的解释要联系到第4章中对变量作用域的解释。
Like Chapter 5, Chapter 6 presumes knowledge of computer architecture, and at least some experience in programming assembly language.
类似于第5章，第6章假定读者具有计算机体系结构知识，并且至少有一些汇编语言编程的经验。
Copyright 2005, Pearson Education, Inc., ISBN: 0-13-147571-1. This excerpt from Chapter 6 is reprinted with permission from the publisher.
Copyright 2005,Pearson Education,Inc.,ISBN: 0-13-147571-1.这则第6章的摘录已得到出版商的许可。
See the section called "Overriding Members of Classes and Traits" in Chapter 6, Advanced Object-Oriented Programming in Scala for more details.
参见《第6章-Scala高级面向对象编程》的“重写Classes和Traits的成员”章节获取更多细节。
See the section called "Overriding Members of Classes and Traits" in Chapter 6, Advanced Object-Oriented Programming in Scala for more details.
参见《第6章-Scala高级面向对象编程》的“重写Classes和Traits的成员”章节获取更多细节。
应用推荐