Jump to content
  • Advertisement
Sign in to follow this  

Virtual Interfaces for Implementation Hiding?

This topic is 2179 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts


I sometimes see people using pure virtual interfaces, especially at module boundaries, to hide implementation details and avoid introducing third-party SDKs into a large number of files.

Using interfaces also seems to complicate design in many cases, and I end up duplicating a large part of each class in separate interface and implementation files. It also seems like the header/source mechanism in C++ was never really designed to separate the interface completely, in the way that Java and C# do.

I'm just wondering what others do to reduce physical coupling and hide implementation details - interfaces? Perhaps the Pimpl/Bridge pattern? Or nothing?

Cheers! Edited by Telios

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!