What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

This question was closed, but it looks like it was done more for pedantic reasons.

What should my Objective-C singleton look like?

The question is really:

How do I create a singleton in Objective-C? Is my solution here appropriate:

They unfortunately phrased it as an opinion question, but it is:

  1. Really a functional question: How can this be done?
  2. May change as the language evolves (some answers could already be modified for ARC)
share|improve this question
It's not really a functional question of "how can this be done?", because the asker has provided a way to do it in the question. It's "can this be done better?", which is pretty Code Review-y and more of a style thing, which can border on unconstructiveness. (Or, in short: what George Stocker said in his comment on the question.) –  U2744 SNOWFLAKE Apr 20 '13 at 21:36
Why would this need to be reopened? It's still there, answered 26 times, unlikely to be deleted, but ultimately better for CR if it were asked now. –  Bart Apr 20 '13 at 21:36
@minitech Just take their answer out of the question and put it in an answer as per Q&A style this site supports. It is a question with multiple answers, as are many questions on SO. –  Ben Flynn Apr 20 '13 at 22:43
@Bart See part two, already some answers could be updated for ARC. –  Ben Flynn Apr 20 '13 at 22:44
Closely related, maybe dupe (its subject is that very question): Suggestions for editing old not constructive question into constructiveness –  Josh Caswell Apr 20 '13 at 22:53
@JoshCaswell Yup. Guess I was late to the party. –  Ben Flynn Apr 20 '13 at 22:58

1 Answer 1

up vote 4 down vote accepted

In general if you think there's a real, answerable question lurking in there, then edit the question to bring it out.

If you have 3,000+ reputation vote to reopen, but even if you haven't the fact you have edited it will add it to the /review/reopen queue where other people can review your edits and vote to reopen if they agree with you.

In this specific case it's probably not worth reopening the question even if you could edit it - which you can't because it's locked. Migrating is not an option either because it's too old (by a long way) and (even it could be migrated) it has effectively been answered so migrating it to Code Review wouldn't benefit anyone.

share|improve this answer
If you think the question needs editing and reopening then edit first. Give the people who view it in the reopen queue something good to look at and a reason why it should be reopened. –  ben is uǝq backwards Apr 20 '13 at 22:14
So I should edit it even though I can't? That doesn't seem like a great solution in this case, though I respect the principle in general. –  Ben Flynn Apr 20 '13 at 22:45
Actually, here we go: stackoverflow.com/questions/7568935/… this basically solves the issue. –  Ben Flynn Apr 20 '13 at 22:47
@BenFlynn - And Colin's answer on the original question is the same as Nick's there. The original question was becoming something of a problem, because it had six duplicated answers (now deleted), some follow-on questions asked in answers, a bunch of wrong answers, and more kept getting added to it. It was becoming troublesome to maintain, which tends to be the result of more open-ended questions. As you can see, a more specific, targeted question ended up not having that same problem. The historical lock guarantees none of that content will be lost even though the question is closed. –  Brad Larson Apr 20 '13 at 23:03
@BradLarson Thanks Brad. Makes sense. –  Ben Flynn Apr 20 '13 at 23:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .