Databases
StackOverflow2013
Postsdbo
POWhy should you ever have to care whether an object reference is an interface or a class?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy should you ever have to care whether an object reference is an interface or a class?
    primarykey
    data
    text
    <p>I often seem to run into the <a href="https://stackoverflow.com/questions/681700/interface-naming-convention">discussion</a> of whether or not to apply some sort of prefix/suffix convention to interface type names, typically adding "I" to the beginning of the name.</p> <p>Personally I'm in the camp that advocates no prefix, but that's not what this question is about. Rather, it's about one of the arguments I often hear in that discussion:</p> <blockquote> <p>You can no longer see at-a-glance whether something is an interface or a class.</p> </blockquote> <p>The question that immediately pops up in my head is: apart from object creation, why should you ever have to care whether an object reference is a class or an interface?</p> <p>I've tagged this question as language agnostic, but as has been pointed out it may not be. I contend that it is because while specific language implementation details may be interesting, I'd like to keep this on a conceptual level. In other words, I <em>think</em> that, conceptually, you'd never have to care whether an object reference is typed as a class or an interface but I'm not <em>sure</em>, hence the question.</p> <p>This is not a discussion about IDEs and what they do or don't do when visualizing the different types; caring about the type of an object is certainly a necessity when browsing through code (packages/sources/whatever form). Nor is it a discussion about the pros or cons about either naming convention. I just can't seem to figure out in what scenario, other than object creation, you actually care about wether or not you're referencing a concrete type or an interface.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMarcus Stade
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy should you ever have to care whether an object reference is an interface or a class?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy should you ever have to care whether an object reference is an interface or a class?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy should you ever have to care whether an object reference is an interface or a class?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't care about the recognize-an-interface-at-a-glance thing. I'm more annoyed about the Impl suffix wart that tends to be used by the don't-prefix-an-interface-with-an-I camp for the first concrete implementation. To me, that's uglier than the I.
      singulars
      1. POWhy should you ever have to care whether an object reference is an interface or a class?
      1. USJasonTrue
    2. COJasonTrue: summed up my thoughts splendidly
      singulars
      1. POWhy should you ever have to care whether an object reference is an interface or a class?
      1. USSteve Ellinger
    3. CO@JasonTrue, I agree wholeheartedly.
      singulars
      1. POWhy should you ever have to care whether an object reference is an interface or a class?
      1. USMarcus Stade
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload