Interfacing and Implementation
Several times on the internet I’ve been in some type of discussion in which I refer to interfaces and implementation. Several times I get a return with some statement about how they aren’t using an interface at this moment, or just explicit confusion to the entire statement all together. Now this doesn’t surprise me, I assumed the person understood the word when they didn’t. It took myself a while to figure out what the hell they are, and that was with both friends and books shoving the concept in my face repeatedly until the light lit up and went ‘ding ding ding!’ This entry here is written in the hopes that it goes ‘ding’ for you as well.
The words are just vocabulary describing concepts. The words travel from 1 language to another easily. It just so happens a few languages also have data types and keywords called the same thing. The only reason these keywords are called that is because the action they perform is equivacle to the definitions of the words as a concept.
Consider it like this… why is a screw called a screw? Because you screw a screw. The name of the screw directly relates to the action performed on or by the screw. I don’t know which definition of word came first (if the noun or the verb), but either way interface is kind of the same idea. We just know that the concept of interface came before the data type interface.
WHAT ARE THEY!? Ok ok, let’s get to the most important part of this article. What the hell is an interface and implementation as a concept.
Well let’s just look at the dictionary definition of this word. It’s not like this word was invented just for programming… it comes from English. Let’s take one of the several definitions of the word that closely relates to our situations from an English perspective.
interface – a common boundary or interconnection between systems, equipment, concepts, or human beings.
The commonality between all the definitions of interface is that it refers to a boundary. And that’s what a programmatic interface is, it’s the exterior boundary of an object. More specifically it’s the parts of an object you can see and communicate with when you aren’t inside the object. I can see a human’s mouth, I can’t see their lungs. His lungs play a large role in their ability to speak, but just from looking at them, it looks as if the mouth is doing all the work. That mouth is their speech interface.
In OOP the interface is nearly the same thing. When you define a class everything inside of the class tends to be protected and wrapped inside of it. This is called encapsulation, and is the simplest example of encapsulation in OOP. Once a Class is instantiated and other objects attempt to use it, the other objects don’t CARE what goes on inside of the Class… and the object doesn’t want the other objects to care. Instead we communicate to the object through its interface… that being the properties and methods defined by the Class.
The word can also relate to other data types as well. Such as user interface, a user interface is the parts of a program as a whole that are made available to a user to alter the program. We don’t let the user into the program to play with anything, we have a definite boundary through which there are a few defined openings they can act upon. Or a graphical user interface, its like a user interface, but displayed as graphics as opposed to command entry (ui is accessed via a shell or command prompt, gui’s are accessed through a more intuitive visual display). Further more larger design patterns can have implicite interfaces. For instance, say you create a large framework… that framework can be designed with implicite boundaries. Certain data types that can be created, and others which are hidden and internal. For instance consider the DisplayList in flash, coders of AS3 don’t get access to the nitty gritty of the DisplayList like how it is rendered or anything. But we have an interface to gain access to it and use it via the DisplayObjects, Stage, and EventDispatchers made available to us. These kind of interfaces are very complex and take a lot of planning. The boundaries of them are sometimes hard to visualize.
When you have an interface, what are we interfacing to? Awww, the implementation. Let’s again take the English definition of the word as a verb (not as a noun).
implement – verb – to put into effect according to or by means of a definite plan or procedure.
And that is exactly what implementation is in programming as well. It the WHAT the interface is allowing you to do. Remember how I described the mouth as the interface of speech for a human. And the lungs played a role in the ability. Well the lungs are part of the implementation. It’s the what that is occuring to allow voice to be created, of course there are other parts that consist in the implementation; larynx, tongue, etc.
In OOP you can see the implementation as the actual operatable code inside of a Class. So the method definition is the interface, and the code inside that method is the implementation. Again though the word isn’t just restricted to OOP and Classes. Anytime there’s an interface, there is an implementation of that interface. In the user interface, the implementation is what occurs when you access some part of the UI. Same for a GUI. Or in a framework the implementation is the entire framework’s structure.
Let’s bring this back into flash again with its DisplayList. I said that the DisplayObjects and the sort act as an interface into this structure. Well the implementation is what the structure is actually doing. Its all the internal code of the flashplayer that renders your DisplayObjects on the stage.
Data types and keywords
So what about the data type interface and the keyword implements. Both these keywords don’t exist in all languages, in more recent languages they’ve been put into use to allow a high level language to easily describe these concepts in code form.
Both of these keywords are explicit rules defined by the language to perform the concepts as defined above. An Interface is a way to describe the interface of a Class. And when a class implements an Interface you are deciding to now write the code which defines the implementation of the Inteface. Yep that’s a lot of reuse of the same word to mean different things… and that’s why it is confusing. But it’s just like the ‘screw’…
I screw the screw with a screwdriver.
See the confusion??? That’s all it is.
I once got in debate with someone about how C++ doesn’t have interfaces, and through out the debate I was trying to explain how C++ does, it just doesn’t have these keywords or the data type. But the concept was there, and you could perform it. The act of extending abstract classes is basically the same idea as implementing an interface. Just abstractly… the only difference was that the same data type could be used to extend and implement certain Classes as well. Still though it’s all there. The same goes for AS3 (which I bring up a lot), it has an interface data type, but you don’t have to use it. I’ve found several open-source projects on the web where the programmer uses an Abstract Class to define the interface. The rule this abstract class is enforcing is the same exact thing as the interface data type.