- Forum
- General C++ Programming
- Issues to take in mind when publishing p
Issues to take in mind when publishing posts
I decided to write a post for those posts that have a rather inappropriate format (and does not help to read them or comment them)
Suggested format for posting threads:
1) Use a descriptive title for your issue.
This will help the possible helpers getting an idea of the problem before opening the post.
2) Do not use capital letters nor phrases like please, urgent etc.
It will not gain you more attention with this. Not will someone help you because you said it's urgent.
3) Use code brackets to publish your code. (this is the firstbottom-right button)
This makes your code more easy to follow and read.
4) Use indentation in your coding for more enhancement of readability.
Less important than previous one though.
5) Explain in simple words what your program was supposed to do.
This will give a clue of the program logic to your readers
6) Explain what exactly is the problems/issues/undesired behavior you are facing.
This will let people go exactly to the heart of the problem than just guessing what it might be.
7) Point out the places where the problem occurs.
This helps also to narrow down the problem. This could be in the form of line of code (provided by the compiler) or even the function/object causing trouble.
I don't know if I missed something (possibly so) but if so I hope others will add it. By this post I do not mean to be cruel to people just posting something here just to have a post to direct them if (too many) requirement of the above are not met.
P.S. If someone know how to add [code] [/ code] without being converted to code output please inform on how.
Suggested format for posting threads:
1) Use a descriptive title for your issue.
This will help the possible helpers getting an idea of the problem before opening the post.
2) Do not use capital letters nor phrases like please, urgent etc.
It will not gain you more attention with this. Not will someone help you because you said it's urgent.
3) Use code brackets to publish your code. (this is the firstbottom-right button)
This makes your code more easy to follow and read.
4) Use indentation in your coding for more enhancement of readability.
Less important than previous one though.
5) Explain in simple words what your program was supposed to do.
This will give a clue of the program logic to your readers
6) Explain what exactly is the problems/issues/undesired behavior you are facing.
This will let people go exactly to the heart of the problem than just guessing what it might be.
7) Point out the places where the problem occurs.
This helps also to narrow down the problem. This could be in the form of line of code (provided by the compiler) or even the function/object causing trouble.
I don't know if I missed something (possibly so) but if so I hope others will add it. By this post I do not mean to be cruel to people just posting something here just to have a post to direct them if (too many) requirement of the above are not met.
P.S. If someone know how to add [code] [/ code] without being converted to code output please inform on how.
Not to be annoying but...
http://cplusplus.com/forum/beginner/1/
As for [code][/code] tags...just put in a bold tag inside one of the leading code tag like so:
[co<b></b>de] <- put bold tag here
http://cplusplus.com/forum/beginner/1/
As for [code][/code] tags...just put in a bold tag inside one of the leading code tag like so:
[co<b></b>de] <- put bold tag here
Finally, a short version. I plan on linking this rather than asking for code tags or clearer problem descriptions.
8) Post the traceback of the error. It may appear to be gibberish to you as a beginner but to an experienced coder it's a gold mine of info that makes it much easier to identify your error.
Topic archived. No new replies allowed.