Same old unfairness!

  • 13
    It depends on the date of the answer to see if it's unfair. Answering the same than other user after a long while gets you downvotes.
  • 11
    They're both terrible answers. You should never have a mutable static member, especially one that's mutated in a non static context
  • 0
    @linux-colonel shouldn't it be compile error?
  • 2
    @crisz no, both solutions would compile. You can reference static members and methods in a non static context, you just can't reference non static in a static context (without an instance of the object)
  • 0
    Yeah, studio may warn this is an activity leak, or something like this, but it compiles anyway. Also, the top answer lacks the "@Override".
  • 0
    That's entire SO's flaw in a picture!
Add Comment