This book should be made an optional reading for in undergraduate computer science student

books:


	• Memory as a Programming Concept in C and C++ Frantisek Franek Cambridge University Press, 2003 - 272 pages average customer review:based on 9 reviews view larger image
	for more information click here

highly recommended

more books need to be written like this

as a C programmer for 3 years now i'm still learning and as you go along you realize how much C is really about memory. This book only served to reinforce that. the examples were great and even the example code he has in there, the only reason i gave it four stars is because the book wasn't bigger. I loved this book and gladly recommend this to any C programmer, budding or veteran.

Another book that will be 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.

for more information click here

This book should be made an optional reading for in undergraduate computer science student

I agree with the other reviewers. In general this is good book. It bridges the gaps between many computer science disciplines. Especially OS and programming language. It also touched a little bit on computer architecture and linking process. The text was written in a a very clear way. However, I do have two complains. The author didn't spend enough effort on the relatively more complex and advanced topics. Eg, linking process for C++, advanced topics in memory leakage detection and prevention. On the other hand, author spent too much energy describing linked data structure in terms of serialization. I personally don't think its relevance is higher than the advanced memory leakage issues. For seasoned profressionals, this book can be used to refresh your knowledge. It is a beginner level to intermediate level book.

for more information click here

Great book

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.

for more information click here

reviews: page 1, 2

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.

for more information click here

hot