You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
1As the question is at the moment, it looks more suited for Code Review, however, since it is not compilable code it is not allowed there. To make the question work better here, and be more than a design review, be sure to add some specific questions you are interested in.Steven Jeuris– Steven Jeuris2011-11-26 15:16:55 +00:00Commented Nov 26, 2011 at 15:16
-
I thought about such a site first but had no idea StackExchange had one. I'll keep it in mind for later, thanks!Seralize– Seralize2011-11-26 15:28:37 +00:00Commented Nov 26, 2011 at 15:28
-
Can you paste the code into the question. Pastebin may not retain the code as long as this question is here. So we need the code on this site to make the questions relevant to the answer.Loki Astari– Loki Astari2011-11-26 15:41:01 +00:00Commented Nov 26, 2011 at 15:41
-
@StevenJeuris: I also think this question would work better on Code Review. I think the question is about reviewing the design of the code so bending the rules is OK in this situation. The spirit of the rule is to prevent people from posting bug fix questions (which belong on stackoverflow).Loki Astari– Loki Astari2011-11-26 15:44:21 +00:00Commented Nov 26, 2011 at 15:44
-
@LokiAstari: Well, the updated question with the two questions at the bottom is very suitable for Programmers in my opinion. If we were to bend the rules and allow not-working code on Code Review the line between Code Review and Programmers wouldn't be that obvious anymore.Steven Jeuris– Steven Jeuris2011-11-26 15:47:36 +00:00Commented Nov 26, 2011 at 15:47
|
Show 4 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you