|
Get your hands on some code, and look at it. Examine it, rip it apart with your thirst for knowledge. You want to know what a certain thing does THEN go to your books. The way I always learned was by looking at it, trying to figure out why. And some people will tell you don't do that, just accept it and keep learning the commands, which is fine, but I always learned by looking at other people's work and figuring out what that did by reading C books, and stuff.
-Delerak
|