Databases
StackOverflow2013
Postsdbo
POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
    primarykey
    data
    text
    <blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/996179/allen-holub-wrote-you-should-never-use-get-set-functions-is-he-correct">Allen Holub wrote &ldquo;You should never use get/set functions&rdquo;, is he correct?</a> </p> </blockquote> <p>Is there a good, no, a <em>very</em> good reason, to go through all the trouble of using getters and setters for object-oriented languages? What's wrong with just using a direct reference to a property or method? Is there some kind of "semantical coverup" that people don't want to talk about in polite company? Was I just too tired and fell asleep when someone walked out and said "Thou Shalt Write Copious Amounts of Code to Obtain Getters and Setters"?</p> <hr> <p>Follow-up after a year:</p> <p>It seems to be a common occurrence with Java, less so with Python. <a href="http://cafe.elharo.com/programming/java-is-dead-long-live-python/" rel="nofollow noreferrer">I'm beginning to wonder if this is more of a cultural phenomena (related to the limitations of the language) rather than "sage advice".</a> As I do not program in Java (currently by choice) I cannot make that assessment.</p> <p>The current (current being as of this writing 2010-03-22) -1 question score is complete for-the-lulz as far as I am concerned. It's interesting that there are specific questions that are downvoted, not because they are "bad questions", but rather, because they hit someone's <em>raw nerve</em>.</p> <p>So let's get to the nut of the matter. I repeat myself:</p> <p><code>What's wrong with just using a direct reference to a property or method?</code></p> <p>And here's the unwritten corollary:</p> <p><code>Are we so undisciplined as programmers that we can't keep our hands off of things that are clearly marked "no touchy"?</code></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USAvery Payne
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    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. POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
      1. USbuti-oxa
      1. VTFavorite
    2. VO
      singulars
      1. POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't feel this is an exact duplicate. The other question asks "Should you *never* use getters/setters?" while this question asks "Should you *ever* use getter/setters?" There's a whole character of difference there!
      singulars
      1. POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
      1. USTalljoe
    2. COD'oh, if this is an exact duplicate, then why the hell didn't it appear in the suggestions when I first posted it?
      singulars
      1. POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
      1. USAvery Payne
    3. CO@Talljoe: That is a subtle difference that had escaped me. Sharp eye! I'll be carefully reading all of the other questions in the Related sidebar that answer this question in order to select a more suitable substitute. Thanks. :)
      singulars
      1. POGetters and Setters: Code smell, Necessary Evil, or Can't Live Without Them
      1. USBill the Lizard
 

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