Guidelines for Posting Requests for Help
version 2

1: When posting code, to help us read your posts please

1. Use code tags.
   1. Start with [c] or [c++]
   2. Then your code
   3. End with [/c] or [/c++]
   For additional information on code tags, see this announcement.
2. Be sure you've formatted you code. Check out this information for tips and ideas.
3. TABs do not work well on the forums so try to use 3-4 SPACEs for indenting.
4. Post only the code that is relevant to the question. You may have to explain how some of the variables are defined.
5. If your code is fairly large, can you
   1. cut out unnessesary sections?
   2. place comments around the section you need help with?
   Posting 200 lines of code with no indication of where we should look is not a good idea.

2: When asking questions be sure to explain fully

1. What your code is supposed to do (what you expected when you ran it)
2. What the code actually does (the result of running it)
3. What you think the solution to the problem might be.
4. If you have compile errors, be sure to mention that fact. Stating "The code does not run" does not mean there are compiler errors. Paste the entire error into your post. Do not paraphrase it. If more than 10 errors, just the first few are enough to start with.
5. Do not use web-speak. This is an English forum, describe your problem in English. Sentences and words, not web abbreviations. You need to communicate what your problem is, and ths duz not hlp u 2 b understood.
6. We understand that for some Engish is not your first (or even second) language. Do the best you can and so will we.

3: Use the Preview Post button before Submitting. You can make sure your post looks the way you want it to look, check spelling, code is formatted, etc.


4: Be sure to list any restrictions you are under.
If you don't, you may get a lot of help explaining how to solve the problem with an array when you were specifically instructed not to use arrays. This wastes everyones time, including yours. Only you know your limitations.


5: Use an appropriate title for your post. Something like

Need help understanding arrays
Using If & Switch in Quadratic equation
Reading and Writing to a text file

Bad titles:
C code prblem -- It's a C/C++ board, duh!
savings account problem -- what is your coding problem, not the assignment
Message Producer -- what does this mean?
Need Help with C++ programming::please:: -- Gee, I was wondering why you were here

And please don't use "urgent", "need help fast", or similar statements in your title. It's not going to get you help any faster and it's annoying -- like we have nothing better to do... Well, we don't, but that's not the point...


6: Do not start new threads on the same topic. Keep replying to the original thread.


7: Do not start a new question on an existing thread unless you are the original poster. New posters should start an new thread unless your question is directly related to the discussion in progress.


8: Don't bump your thread. Most of us have lives outside of the forum so bumping your post after an hour or two is not appropriate. Sometimes it may take up to a day for the right person to read your post. We've got quite a few good people reading your posts, all voluntary, and they do so when they are able. So bumping is unecessary. If someone can help, someone will help.


9: Do not use ALL CAPITAL LETTERS! This is considered shouting and is rude.


10: Limit your smileys. You don't need a smiley on each line (let alone 2 or 3 per line). Use them to enhance your post, not make your post cute.


11: Some examples of bad posts:

http://www.gidforums.com/showpost.ph...87&postcount=1
A blatant request for someone else to do the program. Maybe not what he intended, but that was the request. He asks for help but gave no information on what he needed help with, coding-wise.

http://www.gidforums.com/showpost.ph...32&postcount=1
No code posted. We therefore have no idea what was tried, so can't help fixing the code.

http://www.gidforums.com/showpost.ph...12&postcount=1
Again, no explanation of what the trouble is. Many people here do not download attached code. Post it -- at least the portion you're having trouble with.

http://www.gidforums.com/showpost.ph...49&postcount=1
SHOUTING! Also notice the message from LuciWiz at the bottom. He had to edit the post to add code tags.

http://www.gidforums.com/showpost.ph...07&postcount=1
Do we have any suggestions? Yeah, tell us something! Followed up with:
http://www.gidforums.com/showpost.ph...11&postcount=4
Even when requested, no code tags. Couldn't be bothered to read the specified information? Code is difficult to read because the formatting wasn't preserved.

http://www.gidforums.com/showpost.ph...03&postcount=1
No code. But to his credit he does mention his limitations. That at least helps when we figure out what he needs help with.

http://www.gidforums.com/showpost.ph...73&postcount=1
Too much code. No idea what the problem is -- or even if there is a problem. Is he asking for help in the infinite loop? And the code has no comments explaining what is happening, leaving us to figure out what the program does, and how.

http://www.gidforums.com/showpost.ph...48&postcount=1
No attempt at using the statement he needs help with, so no idea what type of help is needed. Also, the format of the code is terrible.


12: Be sure to check out the Tutorials. Many people have spent a good chunk of time preparing these for your benefit. There's a lot of great information in these threads. Some of the more useful beginner's tutorials:
Formatting C/C++ code -- to help you make your code readable
Standard I/O -- Most of the C I/O calls
Naming Conventions -- Creating names for your variables and functions to make your code easier to understand
Decimal to Hex conversion function -- C++ template function to convert numbers into a hex string. Can be used as a pattern to convert other bases
A Comprehensive Digest of C++ -- A guide to general C/C++ programming components, leaning towards C++. Used old C++ headers -- be sure to translate headers into the non .h form
Pausing a Program to See the Output -- Safe and portable ways to pause your program when run from an IDE
Things to avoid in C/C++ -- Many bad practices are seen often on help boards, and this thread discusses many of them
Pointers in C (Part I) -- Good information on what pointers are and how to use them