Libraries and .h files
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?
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
Popular Topics
Advertisement