AcceleratedC++源代码资源-CSDN文库

共7个文件

html：3个

zip：3个

gz：1个

Accelerated

C++源代码

5星 · 超过95%的资源需积分: 35 97 浏览量 2012-08-16 10:43:13 上传评论 1 收藏 265KB RAR 举报

Accelerated C++源代码本书全面介绍了C++语言。作为一本入门书（Primer），它以教程的形式对C++语言进行清晰的讲解，并辅以丰富的示例和各种学习辅助手段。与大多数入门教程不同，本书对C++语言本身进行了详尽的描述，并特别着重介绍了目前通行的、行之有效的程序设计技巧。　　无数程序员曾使用本书的前几个版本学习C++，在此期间C++也逐渐发展成熟。这些年来，C++语言的发展方向以及C++程序员的关注点，已经从以往注重运行时的效率，转到千方百计地提高程序员的编程效率上。随着标准库的广泛可用，我们现在能够比以往任何时候更高效地学习和使用C++。本书这一版本充分体现了这一点。第4版的改动为了体现现代C++编程风格，我们重新组织并重写了本书。书中不再强调低层编程技术，而把中心转向标准库的使用。书中很早就开始介绍标准库，示例也已经重新改写，充分利用了标准库设施。我们也对语言主题叙述的先后次序进行了重新编排，使讲解更加流畅。除重新组织内容外，为了便于读者理解，我们还增加了几个新的环节。每一章都新增了“小结”和“术语”，概括本章要点。读者可以利用这些部分进行自我检查；如果发现还有不理解的概念，可以重新学习该章中的相关部分。书中还加入了下述几种学习辅助手段：重要术语用黑体表示，我们认为读者已经熟悉的重要术语则用楷体表示。这些术语都会出现在章后的“术语”部分。书中用特殊版式突出标注的文字，是为了向读者提醒语言的重要特征，警示常见的错误，标明良好的编程实践，列出通用的使用技巧。希望这些标注可以帮助读者更快地消化重要概念，避免犯常见错误。为了更易于理解各种特征或概念间的关系，书中大量使用了前后交叉引用。.. 对于某些重要概念和C++新手最头疼的问题，我们进行了额外的讨论和解释。这部分也以特殊版式标出。学习任何程序设计语言都需要编写程序。因此，本书提供了大量的示例。所有示例的源代码可从下列网址获得： http://www.awprofessional.com/cpp_primer 万变不离其宗，本书保持了前几版的特色，仍然是一部全面介绍C++的教程。我们的目标是提供一本清晰、全面、准确的指南性读物。我们通过讲解一系列示例来教授C++语言，示例除了解释语言特征外，还展示了如何善用这门语言。虽然读者不需要事先学过C语言（C++最初的基础）的知识，但我们假定读者已经掌握了一种现代结构化语言。本书结构本书介绍了C++国际标准，既涵盖语言的特征，又讲述了也是标准组成部分的丰富标准库。C++的强大很大程度上来自它支持抽象程序设计。要学会用C++高效地编程，只是掌握句法和语义是远远不够的。我们的重点，在于教会读者怎样利用C++的特性，快速地写出安全的而且性能可与C语言低层程序相媲美的程序。 C++是一种大型的编程语言，这可能会吓倒一些新手。现代C++可以看成由以下三部分组成： l 低级语言，多半继承自C。 l 更高级的语言特征，用户可以借此定义自己的数据类型，组织大规模的程序和系统。 l 标准库，使用上述高级特征提供一整套有用的数据结构和算法。多数C++教材按照下面的顺序展开：先讲低级细节，再介绍更高级的语言特征；在讲完整个语言后才开始解释标准库。结果往往使读者纠缠于低级的程序设计问题和复杂类型定义的编写等细节，而不能真正领会抽象编程的力量。就更不用说学到足够的知识去创建自己的抽象了。本版中我们独辟蹊径。一开始就讲述语言的基础知识和标准库，这样读者就可以写出比较大的有实际意义的程序来。透彻阐释了使用标准库（并且用标准库编写了各种抽象程序）的基础知识之后，我们才进入下一步，学习用C++的其他高级特征，来编写自己的抽象。第一和第二部分讨论语言的基础知识和标准库设施。其重点在于学会如何编写C++程序，如何使用标准库提供的抽象设施。大部分C++程序员需要了解本书这两部分的内容。除了讲解基础知识以外，这两部分还有另外一个重要的意图。标准库设施本身是用C++编写的抽象数据类型，定义标准库所使用的是任何C++程序员都能使用的构造类的语言特征。我们教授C++的经验说明，一开始就使用设计良好的抽象类型，读者会更容易理解如何建立自己的类型。第三到第五部分着重讨论如何编写自己的类型。第三部分介绍C++的核心，即对类的支持。类机制提供了编写自定义抽象的基础。类也是第四部分中所讨论的面向对象编程和泛型编程的基础。全书正文的最后是第五部分，我们在这一部分讨论了一些高级特征，它们在构建大型复杂系统时最为常用。致谢与前几版一样，我们要感谢Bjarne Stroustrup，他不知疲倦地从事着C++方面的工作，他与我们的深厚友情由来已久。我们还要感谢Alex Stepanov，正是他最初凭借敏锐的洞察力创造了容器和算法的概念，这些概念最终形成了标准库的核心。此外，我们要感谢C++标准委员会的所有成员，他们多年来为C++澄清概念、细化标准和改进功能付出了艰苦的努力。我们要衷心地感谢本书的审稿人，他们审阅了我们的多份书稿，帮助我们对本书进行了无数大大小小的修改。他们是Paul Abrahams、Michael Ball、Mary Dageforde、Paul DuBois、Matt Greenwood、Matthew P. Johnson、Andrew Koenig、Nevin Liber、Bill Locke、Robert Murray、Phil Romanik、Justin Shaw、Victor Shtern、Clovis Tondo、Daveed Vandevoorde和Steve Vinoski。书中所有示例都已通过GNU和微软编译器的编译。感谢他们的开发者和所有开发其他C++编译器的人，是他们使C++变成现实。最后，感谢Addison-Wesley的工作人员，他们引领了这一版的整个出版过程：Debbie Lafferty——我们最初的编辑，是他提出出版本书的新版，他从本书最初版本起就一直致力于本书；Peter Gordon——我们的新编辑，他坚持更新和精简本书内容，极大地改进了这一版本；Kim Boedigheimer——他保证了我们所有人能按进度工作；还有Tyrrell Albaugh、Jim Markham、Elizabeth Ryan和John Fuller，他们和我们一起经历了整个设计和制作过程。...

资源推荐

资源详情

资源评论

收起资源包目录

Accelerated C++源代码.rar （7个子文件）

win-source.zip 110KB

macfix.html 2KB

borland-source.zip 105KB

win-net-source.zip 104KB

errata.html 29KB

unix-source.tar.gz 37KB

msbugs.html 12KB

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <title>Accelerated C++ Errata</title> <link rel="stylesheet" type="text/css" href="./acc.css" /> </head> <body> <div class="prevnext"> <a href="109.htm"><img src="images/Prev1.gif" /></a> </div> <h1>Accelerated C++ Errata</h1> <em>Last modified 23 September 2004.</em> <p> Every book has bugs in it, and <cite>Accelerated C++</cite> is no exception. This page notes the bugs that have come to our attention, and the printings in which they were discovered. All of these errors are corrected in the printing after the one in which they were found, except that errors noted in the fifth printing were not corrected until the ninth printing, which went to press in August, 2004. </p> <p> Please note that because of corrections, page numbers may sometimes differ slightly from one printing to another. So, for example, if you have a copy of the first printing, and you are looking for a correction first noticed in the fourth printing, you may find it on the page before or after the one cited. </p> <p> Thanks to Walter E. Brown, Don Caldwell, Paolo Carlini, Neil Cerutti, Harry Chung, David Clark, Anton Doblmaier, Debatosh Debnath, Steven van Dijk, Hans Dulimarta, Daniel Faber, Attila Feher, Adam Foster, Kevin Goodsell, Seyed H. Haeri, Gregory Haley, Mogens Hansen, Philip Hibbs, Anto Jurkovic, John Linderman, Greg McClure, Miguel Mart�nez de la Torre, Bernd Mohr, Wo-Yip Ng, Nicole McAllister, Brian McNamara, Frank Mittelbach, Ron Natalie, John Potter, Peter N. Roth, Andreas Scherer, William Simon, Marc Souaille, Randy Sherman, Ralf Taner, Antoine Trux, Alex Tuzlukov, Abraham Walfish, Conrad Weisert, and Han Xu for pointing them out! </p><h2>Technical errors in the fifth printing</h2> <ul> <li> Pages 32 and 307: The precedence table should say that the assignment and conditional operators have the same precedence and are right-associative. </li><li> Page 173: In the second line from the end of the page, <tt>*beg</tt> should be <tt>*begin</tt> (twice). </li><li> Page 179: The text should say that it is possible for <tt>argc</tt>to be zero. </li><li> Pages 191-192, 314: The types that containers are required to provide include <tt>difference_type</tt> </li><li> Page 223: In the fourth line of the first complete paragraph, <tt>iostream</tt> should be <tt>istream</tt>. </li><li> Page 224: In the fifth line after the second program example, <tt>string</tt> should be <tt>Str</tt>. </li><li> Page 304: The text incorrectly states that <tt>float</tt> is promoted to <tt>double</tt> as part of the standard arithmetic conversions. </li></ul> <h2>Clarifications in the fifth printing</h2> <ul> <li> Page 24: The discussion at the bottom of the page should say explicitly that treating a <tt>bool</tt> value as a number yields <tt>1</tt> if the <tt>bool</tt> is <tt>true</tt> and<tt>0</tt> if the <tt>bool</tt> is <tt>false</tt>. </li><li> Page 216: In the code example at the bottom of the page, the call to <tt>s.data.push_back</tt> is not the only compile error, because it is not the only reference to <tt>s.data</tt>; there is another reference near the beginning of the example. </li></ul> <h2>Typographical details in the fifth printing</h2> <ul> <li> Page 57: In the fourth paragraph, the first sentence should end with ``end-of-file'' instead of ``end-of file.'' </li><li> Page 111: In the last full paragraph, the variable named <tt>didn't</tt> should be <tt>didnt</tt>. </li><li> Page 128: Near the bottom of the page, the sentence that refers to ``the data structure that <tt>split</tt> returns'' should instead be referring to <tt>xref</tt>. </li><li> Page 154: There is a comma missing in the argument list of the call to <tt>copy</tt> in the last line of exercise 8-6. </li><li> Page 219: The constructor of class <tt>Str</tt> should have parameters named <tt>b</tt> and <tt>e</tt>, rather than <tt>i</tt> and <tt>j</tt>, to match the version on page 212. </li></ul> <h2>Technical errors in the fourth printing</h2> <ul> <li> Page 34: In exercise 2-10, the comparison <tt>k</tt> <tt>!=</tt> <tt>n</tt> should be <tt>k</tt> <tt>!=</tt> <tt>10</tt>. </li><li> Page 70: The invariant near the bottom of the page should refer to <tt>maxlen</tt> rather than <tt>max</tt>. </li><li> Page 174: In the third line from the bottom, <tt>coord</tt> <tt>+</tt> <tt>1</tt> should be <tt>coords</tt> <tt>+</tt> <tt>1</tt>. </li><li> Page 183: In the comment in the code example near the bottom of the page, <tt>p</tt> should be <tt>*p</tt>. </li><li> Page 190: In the last code example on the page, <tt>size_type</tt> should be <tt>std::size_t</tt>. Note that the similar example on page 193 is correct as it stands, because <tt>size_type</tt> has now been defined. </li><li> Page 239: The call to <tt>students[i].grade()</tt> is dynamically bound, not statically bound. However, because the type of <tt>students[i]</tt> is known during compilation, the effect is the same as that of static binding. </li><li> Page 264: The first code example should call <tt>s1.read(cin)</tt> rather than <tt>read(cin,</tt> <tt>s1)</tt>, and similarly for <tt>s2</tt>. </li><li> Pages 265-266: The text sometimes mentions the standard <tt>vector</tt> class when it should refer to the <tt>Vec</tt> class that we are defining. </li><li> Page 280: The last code example has a spurious semicolon at the end. </li><li> Page 281: The first complete paragraph should note that <tt>Pic</tt> must also be a friend. </li><li> Page 304: The list of conversions is missing an entry, just before the last one. It should say: ``Otherwise, if either operand is <tt>unsigned</tt> <tt>int</tt>, the result is <tt>unsigned</tt> <tt>int</tt>.'' It also needs to mention the integral promotions. </li><li> Page 307: The description of compound assignment should say <tt>x</tt> <em>op</em><tt>=</tt> <tt>y</tt> instead of <tt>x</tt> <em>op</em><tt>=</tt> <tt>x</tt> </li></ul> <h2>Typographical details in the fourth printing</h2> <ul> The code examples are not consistent about whether to put a space after <tt>template</tt>; that is, whether to say <ol><tt>template<class T> class Vec { /* ... */ };</tt></ol> or <ol><tt>template <class T> class Vec { /* ... */ };</tt></ol> Fortunately, it's correct either way. </ul> <h2>Clarifications in the fourth printing</h2> <ul> <li> Pages 32 and 307: The description of compound assignments in the table should enumerate the operators explicitly. The description of <tt>%</tt> should say that the operands must be integers. </li><li> Page 100: In exercise 5-9, it's not clear whether a word containing mixed-case letters is uppercase or lowercase. The exercise should be to write all the words in the input that do not contain any uppercase letters, followed by all the words that contain one or more uppercase letters. </li><li> Page 179: The program at the bottom of the page can be made easier to understand by writing <tt>argv[1]</tt> as a special case, and then printing a space <em>before</em> each subsequent argument, if any. </li><li> Pages 260 and 263: The initializations of <tt>p</tt> and <tt>refptr</tt> are clearer if they appear in the same order as the definitions of the data members themselves. </li></ul> <h2>Technical errors in the third printing</h2> <ul> <li> Page 47: The invariant in the comment on the third line of the page should say that <tt>hom

评论收藏

内容反馈