# Question closures under PHP tag and and thin pretexts

Recently a question has been closed, with a reason "Code not implemented or not working as intended". However,

• the code (however as silly as it is) is fully implemented and working
• the OP asked several specific questions on the matters that concern them most, that are fully in the scope of this site
• only one of these questions involves an "undesired behavior", in connection with the previously expressed concern about security, so the OP is not certain about that, hence asking the guidance.

This very last sentence has been carefully nitpicked from the question and used as a pretext for the closure. This is a hair splitting to the extent of mockery.

I wouldn't be much concerned if not the overall community response that seems to support the closure, either with commenting and voting. And it is not the first time I see such an attitude. It frightens me. Do I fatally misinterpret the guidelines of this site? If so, please kindly explain.

• I find a lot of your question to be quite rude towards the person that closed it. And seems to extend to people that agree with the closure. You may have a point, but you can be nice about it. – Peilonrayz Apr 9 '18 at 8:12
• There's so many assumptions about intentions of people in this post. Get your assumptions out of this, otherwise people will feel attacked. These assumptions are most likely baseless. In addition to that the conclusions you draw from these assumptions and the questions you ask have a very aggressive tone. I'm somewhat tempted to edit this question just to tone down the aggressiveness, but I'm pretty sure you'd just blow up at me for that. We welcome constructive criticism here, but this just reads as a childish "I AM RIGHT AND YOU ALL ARE NOT!" – Vogel612 Apr 9 '18 at 9:41
• @Vogel612 thank you I've got my answer already. Pity, it's incompetence. – Your Common Sense Apr 9 '18 at 9:49

I've closed the question again. There is no way that the DBConnect object could possibly be useful, when the connect() method does not return anything, and when it only uses local variables (and keeps no state in instance variables).

I conclude that this is either pseudocode or a very sketchy excerpt. Either way, it's not reviewable, as of Rev 2.

• Yes, i noticed that too. I was ok with the closure from the beginning though, what I am objected is a closure under a formal pretext, based on the words taken out of the context. That's a dangerous ground. – Your Common Sense Apr 9 '18 at 13:54
• This isn't necessarily obvious, or easy, and nobody gets it right every single time - see, nobody does. Thanks for stepping in! – Mathieu Guindon Apr 9 '18 at 14:01
• "Pretext" is a loaded word, which implies bad intentions, and basically turned this meta question into a rant. This meta post would have been much better received if it had been worded neutrally. – 200_success Apr 9 '18 at 14:02

Following the editing-out of the last sentence (which I've approved), I've reopened the question.

OP is clearly interested in improving their code, and barring that last sentence the post in on-topic, and the edit does not warp the OP's intent.

I've approved an edit that makes your question perfectly fine. If you want to ask specifically why it's echoing and how to avoid that, feel free to ask that specific question on Stack Overflow. – Mathieu Guindon♦ just now

That said I don't agree with the assessment of incomptence and intentions-interpreting going on here. Often a first-time poster will present code for illustrative purposes only to depict the specific problem they're asking about, and aren't really interested in a review or in improving their code. If all they wanted was an answer to the echoing question, then no edit could have salvaged it: it's indeed usually better to let the OP fix their question themselves, with proper guidance in the comments.

I do agree that sometimes questions are being closed in accordance with the site rules, but on the basis of an OP that is new to this community and doesn't necessarily know what they can and what they can't (shouldn't, anyway) ask in the body of their post. I draw the line at the OP's apparent intent: if they are interested in a peer review, and happened to slip an off-topic request in their post, the question can be saved. This isn't necessarily obvious, or easy, and nobody gets it right every single time.

• Like you, I'm not convinced that unilaterally removing part of the question to bring it back on topic is a good idea. The OP might consider the removed part to be the important bit of the question, in which case it would be better to direct them to Stack Overflow where they would have a chance of getting the answer they need. So in general I think it's better to let the OP make the substantive edits to their own question. – Gareth Rees Apr 9 '18 at 11:45

The reason it was closed was:

Code not implemented or not working as intended: Code Review is a community where programmers peer-review your working code to address issues such as security, maintainability, performance, and scalability. We require that the code be working correctly, to the best of the author's knowledge, before proceeding with a review.

• the code (however as silly as it is) is fully implemented and working

Yes, but it didn't work as the OP intends.

• the OP asked several specific questions on the matters that concern them most, that are fully in the scope of this site

Yes, all bar the last reason look like fine general questions to me.

• only one of these questions involves an "undesired behavior", in connection with the previously expressed concern about security, so the OP is not certain about that, hence asking the guidance.

The OP is asking us to fix their code. They don't know how to fix something themselves, so came here for free help.

• This very last sentence has been carefully nitpicked from the question and used as a pretext for the closure. This is a hair splitting to the extent of mockery.

If we let each and every 'fix my code' question on this site, then we'd soon turn into Stack Overflow. Where people dump their code and expect the community to do their all to fix every problem the user has, for free.

We don't allow 'fix my code' questions as we'd soon stop reviewing code, and just fixing peoples code.

If the question didn't include that last question, I can't see why it'd be off-topic, but if we just remove it then it's likely the OP will be annoyed if we answer the question and don't address it.

• Even provided with the question review that proves it on topic, you are keep insisting on the wrong decision. I find this attitude much more disgusting than blunt but honest indignation. Someone being really nice would have rather edited this question, removing an insignificant formally off topic part, if it bothers them too much. You are being formal and bureaucratic to the extent of mockery. I would have expected such an attitude anywhere but on a programmers' driven site. – Your Common Sense Apr 9 '18 at 8:44
• @YourCommonSense As stated in my answer, if we were 'really nice', the OP would still be annoyed if we don't address that concern. You should probably stop insulting everyone that doesn't agree with you. If you have any concerns that don't boil down to your emotions, then I'd be happy to discuss them. But don't insult me again. – Peilonrayz Apr 9 '18 at 8:49
• Nobody "insulted" you whatsoever, stop pretending that. Also stop pretending to know whether the OP will be "annoyed" or not, you cannot know. I don't know why you are such hostile towards a silly PHP learner who asked a honest question is but it's anything but "being nice". – Your Common Sense Apr 9 '18 at 9:01
• @YourCommonSense The only hostile one here is you. – Peilonrayz Apr 9 '18 at 9:04
• To be honest, a comment by the closing party on the original question would have been great. That way, the original asker could have improved it. Asking for new features or fixing them is—however—off-topic. – Zeta Apr 9 '18 at 9:56