>>7
I've done a bunch of the tuts on cprogramming.com
That has a bunch of weak ass programmers and half the information is incorrect. Be a man and go to a real joint like comp.lang.c.
I've learned a good bit too through looking at other people's codes.
Looking at shitty code doesn't make you a good programmer.
It is a pain though, coding C on Linux but learning from tutorials made for Windows users. Seeing them all trying to include fuctions that don't work on Linux, it's annoying. They assume everyone users Windows. :/
That's because the idiots that write this shit confuse platform specific shit with ANSI/ISO C. Most of us get around this nonsense by either
a)Having include guards in our code.
b)Putting the system specific shit in a different file.
c)Having reasonable makefile rules.
Then after a while, you have the holy vision and you dump the loser language for a real language like Haskell.