然而，它的主题和在其他虚构作品中的位置使这一章既奇特又引人注目。
Nevertheless, its topic and placement in an otherwise fictional work make the chapter as remarkable as it is strange.
它使用了方便的require函数，这个函数是被自动导入到当前的作用域中的(正如我们将在《第7章- Scala对象系统》的“预定义对象”章节所要讨论的)。
It USES the convenient require function that is imported automatically into the current scope (as we'll discuss in the section called "the Predef Object" in Chapter 7, the Scala Object System).
紧跟着讲述画面过渡的一章特别有意思，它雄辩地说明了为何不应该突然地在各个画面间跳跃，而应该清晰地表明画面之间的相互关系。
A chapter on transitions is particularly interesting and presents a strong case for why interfaces should not instantly jump to various screens without making it clear how they relate to each other.
我们中的很多人尝试保存购买接受页面或者产品密钥，去发现当你再一次打开它的时候网页变得杂乱无章。
Many of us have tried to save a purchase receipt page or product key, only to find that the web page looks scrambled when you later open it.
十诫常被称作礼节十诫，记录在《出埃及记》第34章中，在发给你们的材料中有列出，它禁止与迦南人联姻，以防以色列人被怂恿信仰他们的上帝。
This Decalogue, which is often called the ritual Decalogue, so it's listed on there in Exodus 34, bans intermarriage with Canaanites less they entice the Israelites into worship of their gods.
在这本书的第一章它提供了很多强有力的故事，试图打开读者对于宽恕的想法。
The first chapter offers powerful stories chosen to open the reader's heart to the idea of forgiveness.
别泄气，你将在该书第七章中发现没有多少人能真正明白它。
Don't feel bad, no one really does, as you'll discover in chapter seven.
在上个月的一个新闻发布会上，丰田章男说之前的扩展推进可能导致了质量下滑，例如危害它实时的产品系统。
At a press conference last month, Mr. Toyoda said the previous expansion push may have caused it to scrimp on quality, compromising its just-in-time production system, for example.
《边缘地带》杂乱无章，就象它的主题。
"Edgelands" is sprawling and untidy, like its subject matter.
令人遗憾的是，显然由于空间不够，斯塔先生只在书中留下如此小的一角——非常简洁的最后一章，来用加州的过去为它的未来做一些暗示。
The regret is that Mr Starr, doubtless pressed for space, leaves so little room-just a brief final chapter-for the implications of the past for California's future.
第6章是有关无限数据流的问题；我们不能结束这个数据流，它只会无限制地继续下去(开玩笑)。
Chapter 6 is about infinite streams; I couldn't finish it, it just went on and on (okay, joking!).
第13章又离开了分析的主题，它给出了一些有关系统体系结构的定义。
Chapter 13 digresses from the analysis to make some definitions about system architectures.
在最后一章之后，它提到的《PASIV设备技术手册》下载地址没什么可看，伙计们，走开吧。
After the final chapter, and its mention of the online address for the PASIV Device Technical Manual, there's nothing to see, folks -move along.
HRD中的第20章“改善性能”对该主题作了很好的阐述，我们在此将关注它的使用方法。
"Chapter 20 Improving performance" in HRD has pretty good coverage. We will focus on usages here.
它包含了学术以及非学术的多方面信息，每一章包含的练习都很容易让你融入其中。
It contains a diverse range of information from academic and non-academic sources and the exercises that conclude each chapter make it easy to involve yourself with the content.
第8章是本书的核心，它实现了对其他函数进行操作的函数(高阶函数，这可能就是本书得名的由来)。
Chapter 8 is the heart of the book, implementing functions that operate on other functions (higher-order functions, possibly the reason for the title of the book).
“我们正在读一本书的第一章第一行，这本书的页数是无限的……”我不知道是谁写的，可我很喜欢这句话，它提醒我们未来是由自己创造的。
I do not know who wrote those words, but I have always liked them as a 3 reminder that the future can be anything we want to make it.
InfoQ：在第9章你说“由一种语言以及它的工程基本原理预示的最佳实践，与依赖注入提出的最佳实践是相同的”。
InfoQ: on chapter 9 you support that "best practices portended by a language and its engineering fundamentals are the same as those proffered by dependency injection".
第15章应该提及CPAN的AppConfig模块，它给出了一个我认为与标准的PerlGetopt模块不同的而且更好的命令行选项接口。
Chapter 15 should have mentioned the AppConfig module from CPAN, which presents a different and, I think, nicer interface to command-line options than the standard Perl Getopt modules.
该简单方法不能用于使用位置谓词的模式；例如chapter/para[last()] ，它只匹配 para元素，如果该元素是某一章的最后一个元素。
This simple approach can't be used for patterns that use positional predicates; for example chapter/para[last()], which only matches a para element if it is the last one in a chapter.
正如第二章中的Add2Integers这个程序里讨论的，你需要在把每个变量引入程序的时候明确指出它的数据类型。
As noted in the discussion of the Add2Integers program in Chapter 2, you must explicitly specify the data type of each variable when you introduce it into a program.
我们会在《第7章-Scala对象系统》的“scala类型结构”章节讨论Nothing。但是它的名字本身就解释了自己！
We'll discuss Nothing in the section called "the Scala Type Hierarchy" in Chapter 7, the Scala Object System, but its name is suggestive!
这是级联方法(currying methods)所需要的。我们会在《第8章- scala函数式编程》中的“级联(currying)章节讨论它。”
This is required for currying methods, which we'll discuss in the section called "currying" in Chapter 8, Functional Programming in Scala.
在《the BuggreAlleThis Bible》中，还有一个值得一提的地方，在它的《创世纪》第三章中有二十七节，而不是普通的二十四节。
The Buggre Alle This Bible was also noteworthy for having twenty seven verses in the third chapter of Genesis, instead of the more usual twenty four.
连左脸也转过来，在路加第六章29节有，但多数人只知道它出自马太第五章39节。
Turn the other cheek, that's also in Luke 6:29, but most people know it from Matthew 5:39.
利未记十七章十一节是这么说的，它重复了血液的禁忌，它提供了一个基本原理。
Leviticus 17:11 says this; it repeats the blood prohibition, and then it offers a rationale.
我最喜欢的是第十章，因为我喜欢它的标题：“第十章里面没有需要学习的新知识”，一个介绍递归的绝佳标题！
My favorite is Chapter 10 simply because I liked the title: "There's Nothing New to Learn in Chapter 10." What a great title for introducing recursion!
它声称书的总数必须为24卷，因为启示录第四章第十节有24位老者，在上帝的正殿里。
It argues that the books must be exactly twenty-four, because Revelation 4:10 has twenty-four elders in God's throne room.
第八章描述了在一个叫艾城的地方所取得的胜利，它靠近耶利亚哥，第九章讲了基遍居民的故事，他们加入了以色列人，他们是加入以色列的当地人。
Chapter 8 describes the victory at a place called Ai, which is near Jericho. Chapter 9 tells the story of the Gibeonites who join the Israelites; they are a local group that seems to join them.
我曾经得到一条改变生活的建议，与我第三章从朋友那里得到的建议不同，它实用、明智、有效。
I once received another piece of life-changing advice, which, unlike the advice I got from a friend in Chapter 3, 1 find applicable, wise, and empirically valid.
应用推荐