2010-05-09, 12:25 AM
That's how I've always done it.
The advantage/disadvantage stems from when you're going to include the header, because in a subtle way you're prepending the entirety of your includes onto the files they're included in and if you've only got the declarations and pointers in the header you're theoretically not including the whole enchilada in every file that the include is used in.
As far as I know that's all hooey thanks to modern compilers anyhow, since it does all the cross linking and assembling and doesn't actually shove the complete code in multiple places over and over.
Ultimately it's likely stylistic preference and comfortable organizational structure and nothing more.
The advantage/disadvantage stems from when you're going to include the header, because in a subtle way you're prepending the entirety of your includes onto the files they're included in and if you've only got the declarations and pointers in the header you're theoretically not including the whole enchilada in every file that the include is used in.
As far as I know that's all hooey thanks to modern compilers anyhow, since it does all the cross linking and assembling and doesn't actually shove the complete code in multiple places over and over.
Ultimately it's likely stylistic preference and comfortable organizational structure and nothing more.