5 comments about Carbon Programming.

1. The simple title "Carbon Programming", is a hint to the straight forward, no-nonsense style of this book.

   This is THE book on Carbon Programming. I wish it came in hard cover, because it will see a lot of use on my workspace.

   At over 1500 pages, after you've digested all the info contained therein, you can use it to bludgeon the next person who offers you a copy of "Window XPee".

   Buy this book. Write the code.




2. I bought this book a while ago when I started programming for the Macintosh. I was looking for a good Carbon book but this book was not what I had hoped for.
   The problem with the book is that it explains a lot about how to program on Mac OS 8/9.x (which still works in Carbon) but not really how to start with a real Carbon program. Most of the examples use the old event handler but not the new recommended Carbon event handler.
   It also uses the old style *.rsrc resources and not the new much simpler nib-file approch to resources.
   Now that I'm porting my Mac OS X program to Mac OS 9 I find it actually very helpful because it covers a lot of Mac OS 9 stuff.

   Over all I would say if you want to write pure Carbon programs for Mac OS X buy another book. If you also want to learn how to program on Mac OS 9 then it is a good choice. It has example code to every chapter which is very helpful.




3. Ok, that's a lie. Many things have changed since OS 9. But they all build upon what's in OS 9. To do carbon, you need to know how OS 9's apis are structured. Most of the changes in Carbon are behind the scenes on OS 9's existing APIs (for example, HIView, etc). Besides, the important changes in Carbon are listed (namely, Carbon Events). The text focuses on being able to run on both OS X and OS 9. If you don't care, you'd probably want to use NIBs with Interface Builder instead of clunky, overpriced Resorcerer.

   I wish there was a chapter on NIBs. That'd be nice. But you can piece together what's necessary from examples & documentation once you've read the book.

   Simply put, there is no better book on the topic, and this one, while not perfect, is very good. Well written, easy to follow. Just the right number of details, good examples with great explaination.




4. I have this book and it's not worthy, well, maybe to have a hard copy of the API with some good comments, because that's what it is... maybe the code examples will help you some times, but I expected a lot more of a book about Carbon...



5. I got this book to learn Mac OS X programming and was very disappointed. There's way too much info on Mac OS 8 and 9, which is great for people who are migrating old applications; but if you're writing new applications like I am, it just gets in the way. Many screenshots are old and do not look like OS X windows. It talks about CDEF resources, which do not work in OS X; it does not talk about the updated way custom controls are done. Code samples use WaitNextEvent(), which is deprecated. There's nothing on quartz, but lots of info on quickdraw, which is deprecated. Nothing on HIView, OpenGL, etc. It appears that this was a great book in its day, but now, it'll probably just confuse you.

4 comments about Programming in ANSI C.

1. You probably want to learn C so that you can learn C++, right? While this is a more difficult book compared with others, it covers the necessary background for you to tackle C++ (and Java subsequently). Kochan's book is easier, but you need a solid foundation in C to move on to OOP in C++ and Java



2. I havent read the book but what i know is that this book is said to be baybl(incil) of C programming.



3. i havent read the book yet but what i know is that this book is said to be the bible of the C



4. Well, this is an excellent book for the new learners but i couldn't find enough high information for my satisfaction. Anyway, It is a nice book.

No comments about C++ Programming Systematically Explained for Beginners.

2 comments about Real Time Systems and Programming Languages: Ada 95, Real-Time Java and Real-Time C/POSIX (3rd Edition).

1. This book is no good for students, as it has exercises with answers only available to lecturers though a password system.
   The examples are ok but do not help for the exercises so it makes the book imcomplete and very dissappointing, If you need help for real time systems then this is not the book for you, If you just want to read a book this might be ok, but learning is not going to be done.
   (...)



2. This book is great because it covers all the important concepts quite well. I think it is a must for those into real-time programming.

No comments about Class Construction in C and C++: Object-Oriented Programming Fundamentals.

4 comments about Problem Solving With C++: Object of Programming.

1. Wow, what a nice text book



2. This is a great book that easily transitions between topics and is well written(unlike most other programming books). Also, when I had a few questions , I e-mailed the author and he personally gave me a book reccomendation for what to read next...(He suggest reading Soustroupe's advanced material)...



3. I entered college two years ago with almost zero programming experience. I'd made a program once that printed out data based on a couple of if-statements in FutureBasic.

   This book is a super tutorial on the basics of C++ and programming. Like good programming, this book is very modular; we completely skipped class design for my first semester class, and still managed to cover most all of the other topics with a problem.

   The code examples are clear and well-commented. If you are having trouble understanding recursion or pointers, snag this book. It's also a good reference for c-string manipulation.

   I still refer to this textbook at my current programming job.




4. A pretty reasonable textbook for an introduction to the C++ language and a beginning look at object oriented programming and all the data structures and templates and other techniques that this entails.
   
   Methods, operator overloading, constructors, destructors, class members, programming structure, syntax, all that sort of stuff.

No comments about C++ Programming With Macapp (Macintosh inside out).

No comments about Amiga C for Beginners.

1 comments about ANSI C: Problem Solving and Programming.

1. A very nice mid-level overview of the "C" language. He moves right along -- getting to the point and describing concepts in an easy-to-understand manner. For example, his Arrays and Pointers section will help you understand things like arr[2] is same as *(arr+2). I bought this book in '91 and find it is one of the most dog-eared books I own. It is an excellent reference. My only wish is that Kenneth would provide more examples and perhaps on CD. If you're going to be a good "C" programmer and you're new to the language, get this book!

1 comments about Infinite Game Universe, Volume 2: Level Design, Terrain, and Sound (Advances in Computer Graphics and Game Development Series).

1. Ok, this book is a little outdated but I just plowed through this and thought I should do a review while my recollection is fresh.
   
   It gets old real fast to read "But now is not the time or place to cover that topic in any detail" on nearly every other page.
   
   Guy, if you're going to do a third book, please actually make some non-trivial working examples. That's what we're looking for.
   
   I mean, how about create a super-simple Starflight type game with random planets, solar systems, naming scheme? Nothing fancy. I hope your third book in the series will have some, any, meat.
   
   This is such an interesting topic I hope it gets a proper treatment someday.
   
   Asides: Why use the messy realloc/malloc in your examples when stl methods would be so much cleaner?
   
   Why have hard-coded constant numbers littered everywhere, and then spend 5 lines of comments explaining "a real app would never do this". Wouldn't it be easier to just add a #define?
   
   Example bins from the CD do not run on Vista64. Perhaps need to include some support libraries?
   
   Was unable to find an errata section for this book with google, but I know there should be one as I found series errors on the first few pages...