Jump to content
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views

Book review

Sign in to follow this  


As some of you may know, I am currently working on a multithreading solution for my game. Right now we decided to make the Thread a class in itself to improve extendability. But also to ensure there is only one point where we have to maintain code.

As I am a relative programming novice I decided to buy a book about multithreading


A big issue I have with this book is that the theory written in it good. The problem I have is basically that the code written in this book is HORRIBLE for the eye. Yesterday I finally opened the book read the theory, flipped the page to C++ examples and the C++ code was not spaced, everything was crammed together

it looked like something like this

Int main(){
int var;
int hello;
int void hello(int x, int y)

everything was slammed together like this, considering the book was not an A4 but an A5-6 you had a few functions with comments taking 2 pages . It was just impossible to read and understand at the same time. THankfully I could download the code from his site, but come on. Code convention is the first thing you should LEARN. People need to read your code, it shouldn't be a big pile of text.

Another problem I have is that the book focuses on C++,Java and Python. Spreading the theory over 3 programming languages is dangerous, most people require the most help with C++ as itd oes not have a native class of its own. C does have the required WIN32 API calls but its not OOP oriented. More emphasis should be put on C as it requires more time to get working properly. And specially now that most of the Games and standard applications are being moved to a multithreaded approach purely because nearly every PC you buy nowadays has a dual core in it.

OVerall the book is good, but only if your behind the PC using the source code, and not reading it from the book. Its THAT hard to read :(

Sunday I am hoping to release a first review of the C++ code we done so far, and how we have implemented our multithreading approach. Its good to know that things are finally going against :)

Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!