Timeline for Proper action when a Java program fails
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Aug 17, 2022 at 8:44 | history | suggested | Glorfindel | CC BY-SA 4.0 |
broken link fixed, cf. https://meta.stackoverflow.com/a/406565/4751173
|
| Aug 17, 2022 at 8:00 | review | Suggested edits | |||
| S Aug 17, 2022 at 8:44 | |||||
| May 23, 2017 at 11:33 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Mar 18, 2014 at 20:22 | comment | added | Cobertos | The users would just be me and the code maintainers as this is a backend prototype of a system so I think a log file will suffice. As for the singleton, I am actually using a singleton. The main arguments seem to be the coupling (new term for me) and for testing (I've never actually done formal unit testing before) where I can really see the appeal of not having a singleton pattern. Thanks for the info :D. I'll keep this in mind the next time I'm looking at a singleton pattern. | |
| Mar 18, 2014 at 19:52 | history | answered | palacsint | CC BY-SA 3.0 |