Timeline for Why shouldn't I be using public variables in my Java class? [duplicate]
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Oct 22, 2013 at 15:15 | history | closed | Jim G. CommunityBot gnat Kilian Foth | Duplicate of Why do we need private variables? | |
| Oct 22, 2013 at 1:00 | review | Close votes | |||
| Oct 22, 2013 at 15:15 | |||||
| Dec 28, 2012 at 9:33 | history | edited | yannis | edited tags | |
| Nov 23, 2012 at 9:36 | comment | added | COME FROM | Think about what would you need to do if you liked to ensure that "rutaOriginal" is never set to null. Can you do that with a public member variable? And how about that "ganancia" -- doesn't it need to be recalculated after bytesOriginal or bytesFinales changes? With public members your object would not get notified of such changes. | |
| Nov 23, 2012 at 7:29 | answer | added | Nikunj Sanghadia | timeline score: 10 | |
| Nov 23, 2012 at 3:27 | comment | added | Deco | programmers.stackexchange.com/a/170972/42031 is my answer to a similar question which explains the reasons for not using public in Java. | |
| Nov 23, 2012 at 2:28 | vote | accept | Saturn | ||
| Nov 23, 2012 at 1:39 | answer | added | Brian Flynn | timeline score: 28 | |
| Nov 23, 2012 at 1:03 | history | asked | Saturn | CC BY-SA 3.0 |