Timeline for Thread-safe Singleton class
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2013 at 8:22 | comment | added | jalf | @l46kok huh? (1) it does address the question by suggesting other (better) ways to achieve the same, and (2) you do realize that this is on codereview.stackexchange.com, right, and not SO? I'm pretty sure a code review normally involves feedback, even feedback you didn't ask for. | |
| Jan 28, 2013 at 7:30 | comment | added | TtT23 | -1, this kind of answer should be discouraged. It doesn't address the question at all. | |
| Dec 1, 2011 at 8:04 | comment | added | jalf | @GMan: yeah, I got tired of googling it... ;) | |
| Dec 1, 2011 at 8:04 | comment | added | jalf | @Loki: I looked in the FAQ for this site, and didn't see anything that discouraged answers like this. It says that if you are looking for "specific feedback about <snip> Best practices and design pattern usage in your code", this is the right side. And that "any aspect of the code posted is fair game for feedback and criticism." If I'm conducting a code review, the first thing I try to find out is "is this the right solution to the problem". I considered posting it as a comment, but to be honest, I think it's valid as an answer. | |
| Dec 1, 2011 at 0:07 | comment | added | Loki Astari | -1: Does not answer the question. He is not asking weather a singelton is good bad ideas. You could just as easily have posted this as a comment. | |
| Nov 30, 2011 at 22:46 | comment | added | GManNickG | I didn't realize you had a form of the URL that's easily memorized. :) Yay. | |
| Nov 30, 2011 at 21:35 | history | answered | jalf | CC BY-SA 3.0 |