What is the seperate implementation interfact class idiom and when do I use it?

Question

I have occasionally come across what I can only describe as the "interface-implementation idiom", where a class is separated into an "interface class" and an "implementation class".

What is the philosophy or reasoning behind this?

What is an example usage of this methodology? What does an example of such a class system look like and why would it be useful to separate a class into an interface and an implementation?

Defining an interface can have one or more out of many reasons. As it is now this question is too broad. — TobiMcNamobi, Aug 03 '15 at 15:26

score 0 · Answer 1 · edited May 23 '17 at 12:15

0

I think what you're talking about is also known as the pImpl pattern. There is lots of discussion about it at Why Should the pImpl idiom be used. That question is also marked as a duplicate of an older question/answer with more information.

edited May 23 '17 at 12:15

Community

1
1

answered Aug 03 '15 at 15:28

Wayne Tanner

1,316
11
18

What is the seperate implementation interfact class idiom and when do I use it?

1 Answers1