Thread: Question about interfaces

I really just suspect this, but I'm asking to confirm one way or the other.

In the study books I have read about interfaces, all of the examples I have seen so
far show the interface being created, then the functions placed in whatever class
they seem to be working with at the time. Yet they say that you create interfaces
so that they can be used by more than one class or project type. This leads me to
believe that perhaps in the real coding world, you would actually create the interface
and the implementation separate, and then just use it in whatever class you are
working on as the need arises. The reason I think this makes more sense is it
seems a cleaner approach as opposed to mixing it in with a class that you could
very well end up discarding, which would then break the functionality of any other
classes you used the interface in. Am I correct?

Originally Posted by Norm

You should at least fix the line breaks when you copy and paste text into a forum.

You have drawn the wrong conclusion; I did not paste this in. I use a 42" television
as my computer monitor . . . . hence the "wideness".

Yes implementation can be many for a single interface. For Example you can have an interface called car and in turn this interface could be implemented by many like Ford,Toyota,Honda etc.