query: Coding to interfaces?
positive_passages.docid: 855
positive_passages.text: What does it mean to "program to an interface"?
negative_passages.docid: 59895
negative_passages.text: When defining a Windows API interface in C#, do I have to define all members? Can I only define the methods I'm going to use?
negative_passages.docid: 43837
negative_passages.text: Implementing interface properties in interfaces with a setter?
negative_passages.docid: 69315
negative_passages.text: Should you always Code To Interfaces In Java
negative_passages.docid: 103758
negative_passages.text: Why are interfaces not [Serializable]?
negative_passages.docid: 41552
negative_passages.text: Do interfaces inherit from Object class in java
negative_passages.docid: 140485
negative_passages.text: Do interfaces really need to "look good"?
negative_passages.docid: 75561
negative_passages.text: Comment the interface, implementation or both?
negative_passages.docid: 5245
negative_passages.text: When should I use an interface in java?
negative_passages.docid: 23198
negative_passages.text: Why explicit interface implementation?
negative_passages.docid: 150881
negative_passages.text: implicit vs explicit interface implementation
negative_passages.docid: 152816
negative_passages.text: Abstract base classes that implement an interface
negative_passages.docid: 85865
negative_passages.text: Optional Methods in Java Interface
negative_passages.docid: 53942
negative_passages.text: Why Doesn't C# Allow Static Methods to Implement an Interface?
negative_passages.docid: 113976
negative_passages.text: Methods visibility in interface
negative_passages.docid: 40842
negative_passages.text: Find Java classes implementing an interface
negative_passages.docid: 50083
negative_passages.text: Cast interface to its concrete implementation object or vice versa?