Members - Reputation: 387
Posted 06 July 2012 - 04:24 AM
I got this book 9 years ago. took me a while to remember which book had the toon shader in it but.
The point is keep your books for later use.
Members - Reputation: 408
Posted 06 July 2012 - 09:51 AM
Crossbones+ - Reputation: 1074
Posted 06 July 2012 - 10:55 AM
I do the quick read because it's easier to understand what is being explained by having an idea about what will happen after.
Edited by TiagoCosta, 06 July 2012 - 10:56 AM.
Aqua Engine - my DirectX 11 game "engine" - In development
Members - Reputation: 3830
Posted 06 July 2012 - 03:39 PM
You don't "finish" a programming book; it's not something you read like that. It goes on your bookshelf and you constantly pull it out again and refer to specific topics for guidance, inspiration and sanity-checking. I still haven't "finished" my old Herb Schildt TurboC reference from 20+ years ago.
It appears that the gentleman thought C++ was extremely difficult and he was overjoyed that the machine was absorbing it; he understood that good C++ is difficult but the best C++ is well-nigh unintelligible.
Members - Reputation: 188
Posted 07 July 2012 - 11:45 AM
Sometimes you just want to get a different person's perspective, but you are already an expert on the subject.
Sometimes it's a new subject and you have to learn to think differently (the graphics pipeline comes to mind here).
Members - Reputation: 644
Posted 11 July 2012 - 03:54 AM
And last but not least, it also depends on what do you mean by "finish a book". :-)
Members - Reputation: 209
Posted 11 July 2012 - 04:39 PM