Thread: Constructive criticism highly appreciated!

you'll see postings and hear comments about programmers that don't document thier code well, yet very rarely will you see an example of how that documentation should be done.

the level in the exapmle I posted can be concidered overkill, but if it gives you an idea of a way to document the code so you aren't part of the problem it's worth it. ~l~

Originally Posted by muggizuggi

Dae, I have taken your advice, and looked into books...
I had the chance to read through the introduction part of The C++ Programming Language, Special 3rd Edition, during my vacation.
I must say, that I didn't find it to be a very good learning book, even if it did clear up a few things (like the virtual-thing, look below!).
It seems like it was written for people who already know how to program in C++, and I may very well get it later, as a reference.

I also looked in C++ Primer Plus earlier, and I found it a bit.... Old fasioned... A bit of a drag to read, know what I mean?
Not good for a highly motivation driven, but poor reader like me.

However, I stumbled on Accelerated C++, by Andrew Koenig and Barbara Moo. Very interesting, new approach to teaching the language. Not as many pages as other good books, but still very thorough (or so I read). Perfect!
I am expecting my copy tomorrow. DROOL!

Yeah The C++ Programming Language is more of a reference, and to clear things up, ..less of a teaching book.

I personally dont mind reading boring books as long as its teaching me something, and C++ Primer Plus is a great starting book, especially if your excitement comes out of the fact you are learning, and not that the book is interesting. Although, I would love to pick up a book that calls me a rabbit all the time.. its fun to read those books, "Alright, rabbit, now that you've gotten down the bunny hole.. lets introduce you to functions. Think of functions as carrots that you pull down from underground, they are there and you can pull the one you want down into your hole, int main (), whenever you want.".

One thing about Structures for Game Programmers is you will know many parts from the book (linked lists, arrays, binary trees, etc.) but it rehashes it for you, adds more information for clarity and I find that many people may know how to use a linked list or array and such, but dont know what they could possibly do with their knowledge game-wise, and this book IMHO gives you some ideas. The actual structures used and methods used in this book arent too advanced though so dont expect them to make you a professional, which is the biggest complaint about the book; other than that the author explains well, includes everything necessary in the book, and gives ideas of how to use your OOP/etc skills. One part I like, though some others didnt, is he goes into making classes that act as an array with methods to do certain things, adding operator overloading, search, add, delete, insert, etc. so it almost resembles STL's containers, which makes understanding them easier and gives you ideas.

Accelerated C++ seemed like a great beginners book too. I had it on my list to reads, but since I've already studied, understood and learned most of the topics.. I dont need it explained again, but rather a book that you can learn from, and use as more as a reference (for when you dont remember, like C++ Primer Plus) or has detailed information (like The C++ Programming Language). Basicly if you've read 2 books/tutorials on C++ then Accelerated C++ isnt the best choice, but otherwise.. a great pick.

I'm actually on vacation ATM

- Oh and of course you have read the amazon.com reviews of the books.. key features in a book for you may be: great book, for beginners, easy to read, interesting; but personally 'can be used as a reference' is a big one for me, since it takes a month or less to read a book.. itd be nice to buy a book that you keep on your desk and keep referring to.