Sign in to follow this  

Virtual Interfaces for Implementation Hiding?

This topic is 1965 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

Hiya,

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

This topic is 1965 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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this