interfacing: simplified

Posted by code wombat on Stack Overflow See other posts from Stack Overflow or by code wombat
Published on 2012-03-21T17:13:04Z Indexed on 2012/03/21 17:29 UTC
Read the original article Hit count: 224

Filed under:
|
|
|
|

i've been doing some research on interfaces and a simple layman's explanation for what it truly is. For some reason people love using overly complex explanations and jargon to explain truly simple concepts (guess it makes them feel big) and i have a gut feeling it's the same in this case.

so from what i could grasp, it seems like interfaces are nothing more than a way to reserve method names, their return type if any, and the type and amount of arguments they accept. so when a class implements an interface (or interfaces) it is forced to define the body of each method from the interface(s). Am i on the nose with this one or do i need to keep digging?

p.s. i know javascript doesn't have support for interfaces, but i still need to understand the concept because there are quite a few places where it's shown how to emulate to an extent.

© Stack Overflow or respective owner

Related posts about c#

Related posts about java