Which book I should buy

Chillbon 2002-04-30 11:00:27

我想买一本有关C++的外文书，可以介绍一二吗？

...全文

43 5 打赏收藏转发到动态举报

写回复

用AI写文章

5 条回复

切换为时间正序

请发表友善的回复…

发表回复

williamcl 2002-05-01

打赏
举报

1.《The C++ Programming Language Special Edition》,by Bjarne Stroustrup(the creator of C++) (Hardcover).February 15, 2000.1040 pages,Addison-Wesley Pub Co.

《The C++ Programming Language(Special Edition)》,高等教育出版社,2001年8月影印版.55.00元.绝对应该买此书.

2.《Accelerated C++:Practical Programming by Example》,by Andrew Koenig , Barbara E. Moo ,Addison-Wesley, 2000 ,ISBN 0-201-70353-X.Paperback.

对于Beginning/Intermediate level,购买上面两本书及《Addison Wesley：C++ In Depth series》(http://www.awl.com/cseng/series/indepth/index.shtml)的其它的书足够了.

这些书马上就要出中文版了.
http://www.china-pub.com/member/bookpinglun/viewpinglun.asp?id=5217
http://www.china-pub.com/computers/epub/newbook/dianli.htm

更多的书请参看http://www.accu.org/ & http://www.amazon.com/.

love4cz 2002-04-30

打赏
举报

错了,应是C++ Primer

love4cz 2002-04-30

打赏
举报

Essential C++

C++ Promer

ironsmith 2002-04-30

打赏
举报

the c++ programming language --stroustrup

晨星 2002-04-30

打赏
举报

《Thinking in C++》物超所值！

In this book we will create a programming language together. We'll start with 0 lines of code and end up with a fully working interpreter for the Monkey* programming language. Step by step. From tokens to output. All code shown and included. Fully tested. Buy this book to learn - How to build an interpreter for a C-like programming language from scratch - What a lexer, a parser and an Abstract Syntax Tree (AST) are and how to build your own - What closures are and how and why they work - What the Pratt parsing technique and a recursive descent parser is - What others talk about when they talk about built-in data structures - What REPL stands for and how to build one Why this book This is the book I wanted to have a year ago. This is the book I couldn't find. I wrote this book for you and me. So why should you buy it? What's different about it, compared to other interpreter or compiler literature? - Working code is the focus. Code is not just found in the appendix. Code is the main focus of this book. - It's small! It has around 200 pages of which a great deal are readable, syntax-highlighted, working code. - The code presented in the book is easy to understand, easy to extend, easy to maintain. - No 3rd party libraries! You're not left wondering: "But how does tool X do that?" We won't use a tool X. We only use the Go standard library and write everything ourselves. - Tests! The interpreter we build in the book is fully tested! Sometimes in TDD style, sometimes with the tests written after. You can easily run the tests to experiment with the interpreter and make changes. This book is for you if you... - learn by building, love to look under the hood - love programming and to program for the sake of learning and joy! - are interested in how your favorite, interpreted programming language works - never took a compiler course in college - want to get started with interpreters or compilers… - ... but don't want to work through a theory-heavy, 800 pages, 4 pounds co

Introduction This book is designed to help all programmers who have ever written their own software to better protect their software from illegal copying. It will also be useful to programmers creating freeware who wish to protect their source code. The idea to write a book like this came to me some time ago when I realized how poorly the topic is covered and how difficult it is to acquire the information necessary to adequately protect software. When I was involved with game production in the Czech and Slovak Republics, I was astonished at how simple their protection was, and that very often they had no protection at all — yet it is so easy to protect software, at least at a basic level. The problem lies in the lack of information and experience in this field. That's why I wrote this book, which will present many previously unaddressed topics concerning software protection. Protection as a Deterrent My experience tells me that there is no protection that cannot be easily removed and, as such, much of the work you will put into protecting your software is simply a deterrent, delaying the inevitable. It's only a matter of time, possibilities, and patience before a cracker cracks your software. Of course, the better your deterrent, the more time you'll have to sell your software before you find it available (or crackable) for free, online. What creators of a program or game would want to find their product, whether shareware or commercial software, pirated on the Internet the very day of the release? That would definitely result in reduced sales. Good software protection prevents the cracker from removing the protection correctly. With such protection, the program won't work, or won't work correctly, and more people will buy an original copy. Of course, a successful crack will appear in the course of time, but the time you buy is money earned. Really good protection will buy a considerable amount of time and will engender several versions of the crack, some of which w

Even as you read this content, there is a revolution happening behind the scenes in the field of big data. From every coffee that you pick up from a coffee store to everything you click or purchase online, almost every transaction, click, or choice of yours is getting analyzed. From this analysis, a lot of deductions are now being made to offer you new stuff and better choices according to your likes. These techniques and associated technologies are picking up so fast that as developers we all should be a part of this new wave in the field of software. This would allow us better prospects in our careers, as well as enhance our skill set to directly impact the business we work for. Earlier technologies such as machine learning and artificial intelligence used to sit in the labs of many PhD students. But with the rise of big data, these technologies have gone mainstream now. So, using these technologies, you can now predict which advertisement the user is going to click on next, or which product they would like to buy, or it can also show whether the image of a tumor is cancerous or not. The opportunities here are vast. Big data in itself consists of a whole lot of technologies whether cluster computing frameworks such as Apache Spark or Tez or distributed filesystems such as HDFS and Amazon S3 or real-time SQL on underlying data using Impala or Spark SQL. This book provides a lot of information on big data technologies, including machine learning, graph analytics, real-time analytics and an introductory chapter on deep learning as well. I have tried to cover both technical and conceptual aspects of these technologies. In doing so, I have used many real- world case studies to depict how these technologies can be used in real life. So this book will teach you how to run a fast algorithm on the transactional data available on an e-commerce site to figure out which items sell together, or how to run a page rank algorithm on a flight dataset to figure out the most important airports in a country based on air traffic. There are many content gems like these in the book for readers.

Ifyou’re embarking on a Python development project, then you should buy this book—there’s nothing quite like it. I know this because I was looking for it last year, and I couldn’t find it. This book introduces the tools you’ll need to get started on agile projects in Python, and unlike any other book out there, it shows you how to tie them all together. Sure, there are many good books on agile development. A lot of them cover the develop- ment processes in great detail, and this is a good thing. Agile development is very much about human interactions and the environment surrounding software development, but there is a whole ecology of tooling to make everything work at a practical level. Agile development eschews extensive up-front specification, and it anticipates that the product will constantly change, but it puts in place rigorous checks to compensate for antici- pated change. Testing is an integral part of agile development from the very start, and it is pursued with ferocious rigor. You need software tools to facilitate testing. Agile projects have very short release cycles, and this has implications for tooling, too. There’s no way to have two-week release cycles if it takes you days to integrate changes, days to perform QA, and days to package and deploy the software. This means that agile develop- ment puts a high value on build and release automation. While agile development techniques can be applied to any project, both testing tools and build automation tend to be very language specific. These tools do exist in Python. They’re widely available, and by and large they’re free, too, but the documentation tends to be . . . um . . . spotty. And while there may be documentation on the individual tools, the documenta- tion telling you how to tie these tools together is usually sparse to nonexistent. This book provides that missing documentation. Who This Book Is For This book is written for a person who knows how to program and is already familiar with Python. Ifyou havesome Python under your belt and you’re thinking of starting a new project, but you don’t know how to get started, then this book is for you. If you’re an experienced Python programmer and you want to give this agile stuff a whirl, then this book is for you. If you’rearelease engineer who has been thrown headlong into the world of Python, then this book is for you, too. If you’re brand new to programming or don’t really know Python, this is not the best book to startwith. Thereare some wonderful books out there that will introduce you to the language,but this isn’tone of them. xix 9810FM.qxd 6/3/08 2:37 PM Page xix What’s Really in Here? Each chapter in this book addresses a different aspect of tooling in an agile development envi- ronment. These are collected roughly into two parts, with the first focusing on basic tooling, and the second focusing on specific practices. If you’re already familiar with Subversion, Setuptools, and Buildbot, then you should have no problem jumping between Chapters 6 through 11. If you’re not, then you’ll want to look at the earlier chapters first. Chapter 1:What Is Agile Development? Chapter 1 provides an overview of the methods that characterize agile development method- ologies, with a focus on those not directly related to tooling. Chapter 2:The IDE:Eclipsing the Command Line This book uses the command line throughout, but modern IDEs provide many benefits. This chapter introduces you to Python development using Eclipse and the Pydev plug-in. Chapter 3:Revision Control:Subverting Your Code Arevision control system is part of the core infrastructure for any agile development environ- ment. Subversion is an excellent choice. I show you how to use it from the command line and from Eclipse using the Subversive plug-in. Chapter 4:Setuptools:Harnessing Your Code You can’t replicate your work for testing purposes without some sort of a framework. In Python, a natural choice is Setuptools,which provides a solid basis for automated builds. Chapter 5:A Build for Every Check-In Automated build systems formthe coreof a continuous integration system. HereIintroduce Buildbot, an excellent system that happens to be written in Python. It ensures that the code you check in builds correctly. Chapter 6:Testing:The Horse and the Cart Unit testing ensures that your code runs as you expect it to, and it prevents regression (reappearance of old bugs) when you change existing code.Iintroduce the unit-testing pack- ages unittest and Nose, and I show how to use Nose to run tests from within Eclipse and Setuptools. Finally, I show how to link them into Buildbot. Chapter 7:Test-Driven Development and Impostors Test-driven development (TDD) is the practice of writing tests before writing the code they test. Imposters (a.k.a. mock objects) provide a powerful unit-testing technique to isolate units of code. I examine two mock object frameworks, pMock and PyMock, and I work through a sizable example to show how TDD, refactoring, and imposters are used, and how they affect the code that you produce with them. IINTRODUCTION xx 9810FM.qxd 6/3/08 2:37 PM Page xx Chapter 8:Everybody Needs Feedback Improving your code requires feedback—useful information that sometimes comes from your coworkers, and sometimes from software. Accurate feedback requires standards. This chapter looks at code coverage, complexity measures, and development velocity. It also examines cod- ing standards, how they can be enforced from within Eclipse, and how you can prevent bad code from reaching your repository by using Subversion pre-commit hooks. Chapter 9:Databases Databases are very widely used these days, and they pose their own special challenges for agile development. This chapter examines the object-relational mappers SQLObject and SQLAlchemy, and then examines how to version databases using the DBMigrate tool. Chapter 10:Web Testing The web is everywhere, and web development has its own set of issues. This chapter examines general approaches to testing web applications, and introduces HTML/XML verification using ElementTreeand BeautifulSoup.It also looks into JavaScript unit testing with JsUnit. Chapter 11:Functional Testing This chapter examines functional testing with a particular emphasis on acceptance testing using PyFit. The chapter shows how to use PyFit, and more importantly, how to tie PyFit into Setuptools and Buildbot. (In my view, this alone is worth the price of the book.)

VC/MFC

16,473

社区成员

421,731

社区内容

发帖

与我相关

我的任务

社区管理员

加入社区

近7日
近30日
至今

加载中

查看更多榜单

社区公告

VC/MFC社区版块或许是CSDN最“古老”的版块了，记忆之中，与CSDN的年龄几乎差不多。随着时间的推移，MFC技术渐渐的偏离了开发主流，若干年之后的今天，当我们面对着微软的这个经典之笔，内心充满着敬意，那些曾经的记忆，可以说代表着二十年前曾经的辉煌……
向经典致敬，或许是老一代程序员内心里面难以释怀的感受。互联网大行其道的今天，我们期待着MFC技术能够恢复其曾经的辉煌，或许这个期待会永远成为一种“梦想”，或许一切皆有可能……
我们希望这个版块可以很好的适配Web时代，期待更好的互联网技术能够使得MFC技术框架得以重现活力，……

试试用AI创作助手写篇文章吧

+ 用AI写文章