Libraries and .h files

Started by
1 comment, last by Red Ant 16 years, 7 months ago
I've always stood by the doctorine of each .cpp file having its own corresponding .h file. It's worked wonderfully so far. But what if I'm writing a library? I want the users to have access to all the functionality, but I don't want all the users to have to include a massive bunch of header files. How would I go about doing this?
NextWar: The Quest for Earth available now for Windows Phone 7.
Advertisement
Make one main header file which includes all the other header files.
But don't just mindlessly include every header in your project. Think about which ones are really needed and which ones aren't actually part of the interface a user will see.

This topic is closed to new replies.

Advertisement