Memory as a Programming Concept in C and C++ | 
 enlarge | Author: Frantisek Franek
Publisher: Cambridge University Press
Category: Book
List Price: $44.99
Buy New: $24.50
You Save: $20.49 (46%)
New (15) Used (9) from $23.98
Avg. Customer Rating:  10 reviews
Sales Rank: 509317
Media: Paperback
Number Of Items: 1
Pages: 272
Shipping Weight (lbs): 0.7
Dimensions (in): 8.9 x 5.9 x 0.7
ISBN: 0521520436
Dewey Decimal Number: 005.435
EAN: 9780521520430
ASIN: 0521520436
Publication Date: November 17, 2003
Availability: Usually ships in 1-2 business days
Condition: BRAND NEW BOOK, CLEAN AND UN-USED. SHIPPED SECURELY IN A BOX.
|
| Also Available In:
|
| Similar Items:
|
| Editorial Reviews:
Product Description
Assuming readers have a basic familiarity with C or C++, Frantisek Franek describes the techniques, methods and tools available to develop effective memory usage. The overwhelming majority of "bugs" and crashes in computer programming stem from problems of memory access, allocation, or deallocation. Such memory related errors are notoriously difficult to resolve. Moreover, the role that memory plays in C and C++ programming is a subject often overlooked in courses and in books. Most professional programmers learn about it entirely through actual experience of the problems it causes.
Book Description
The overwhelming majority of bugs and crashes in computer programming stem from problems of memory access, allocation, or deallocation. Such memory related errors are also notoriously difficult to debug. But the role that memory plays in C and C++ programming is a subject often overlooked in courses and in books. Most professional programmers learn about it entirely through experience of the trouble it causes. This book provides students and professional programmers with a concise yet comprehensive view of the role memory plays in all aspects of programming and program behaviour. Assuming only a basic familiarity with C or C++, the author describes the techniques, methods, and tools available to deal with the problems related to memory and its effective use.
|
| Customer Reviews: Read 5 more reviews...
 Very good information for the undergrad CS major November 25, 2008
This is written for the programmer who isn't sitting in front of their computer. Because of this, the book is very readable. If you can go through this book and understand the concepts, you will be worlds ahead of most CS undergrads in their first year. It really ought to be required reading.
 This book = training wheels August 24, 2008
0 out of 1 found this review helpful
I really can't agree with the other reviews. The content of this book is on the basic side of things. It should be purchased if, and only if (big 'only if'), you are in the process of learning C or C++. A programmer with more than just an introductory knowledge of these two languages should be able to figure out all of the implemented programs in the text. The concepts about memory and memory use should have either 1) been taught to you when you learned to program or 2) again, you could have figured it out on your own. Furthermore, the book is incredibly overpriced, however you measure it- page count, content value, whatever- it doesn't add up to the cost.
Franek is clearly on the OOP bandwagon. The discussion of C is just a formality, I think, because at every turn he takes a shot at how bad memory management and leaking is in C programs. To me, this says he doesn't really know how to use the language (and/or an IDE with debugging tools) properly. By my estimation, C++ is more prone to memory problems...the joke about shooting yourself in the foot in various programming languages comes to mind.
Pass on this book. You can find more and better information elsewhere. Search Amazon for more memory management books, or a book on garbage collection.
The book has little theory, and talks more about implementation details than anything else. May 17, 2008
0 out of 2 found this review helpful
I bought this book thinking I would get more insight about memory models in C and C++ languages. And how memory is a different resource. With its typed and untyped properties. With discussions about C++ RAII etc.
I was very disappointed to find out that this book is actually an weak explanation of how compilers implement the object model.
Great book April 12, 2007
5 out of 8 found this review helpful
First I would like to state the reason I gave it 4 stars. In my opinion, 5 stars should be very hard to reach. Maybe I would give this 4.5 stars if it was possible. Anyway, I'm a self taught VB 6 programmer with a working knowledge of the Windows API. First year CS student, though I've read many a book on C and a few on assembly. I have a large CS library and this is the first book of it's kind that I've found. It is a little pricey if you compare book size to other, larger CS books, but I don't think it is overpriced. The material is great, though I wouldn't say it is a beginner level book. I had trouble grasping enough of the material that it causes me to think either I've still got a long ways to go in learning (more so than I thought at least), or it is just not for the beginner.
I would recommend this book to anyone who is serious about a programming career, regardless of the language. The book's relatively small size should not be a negative factor. It is not densely packed with information to the point where interpretation is needed, instead it explains in sufficient detail without dumbing it down by over-repetition and such used by some other CS books. It is aimed at C/C++ programmers, so being familiar with those is a prerequisite, obviously. Like another reviewer said, there seemed to be a little too much discussion on, say, serialization of linked data structures, an important topic with regards to memory yet I felt a little more emphasis could have been placed elsewhere.
Another book that will be helpful October 2, 2006
4 out of 4 found this review helpful
An older book that could be helpful to readers interested in this book is "Inside the C++ Object Model" by Stanley B. Lippman. It was written in 1996. It shows things such as the layout of C++'s organization of (pointers to) virtual and inherited methods.
|
|
|
