January 7th, 2002, 09:43 PM
New users - HOW TO POST A QUESTION - READ THIS FIRST
C/C++ FORUM SPECIFIC RULES
(Thanks Schol-R-Lea for text)
Let us know what the tools you are using are, particularly the language, compiler(s) and operating system(s) being targeted. This is especially important on this forum, given that it covers more than one language; the usual assumption here is that you are using C++, and if you are using one of the other languages covered (C, C#, Objective-C, or the variants of those), it is important to mention that to avoid confusion. Similarly, there are many commonly used operating systems (Windows, MacOS, Linux, and the BSD Unices) and many commonly used compilers (Visual C++ 6.0, 7.0, 7.1, Borland C++ Builder, various versions of gcc etc.), and in many cases the differences between them are relevant.
One good way to do this is in the message title, in square brackets either before or after the main description, like so:
"[Obj-C, MacOS] linking Cocoa programs with assembly object files"
Also, if the question is about the build process (compiling, linking, project or make files, etc.), you should mention the IDE or make system you are using (VC++, Dev-C++, Code::Blocks, etc.), if any. If any third party libraries are being used, these should be mentioned as well.
GENERAL POSTING RULES
Originally posted by JeffCT on 10-19-2001 03:51 PM in PHP Forum
I figured this was necessary because a lot of people come in and post threads without thinking, and without realizing that there is no possible way they could get help because of the way they posted the question. Here are some general guidelines.
USE SEARCH FIRST!
There is a pretty good chance that unless you have some
really odd or unique problem that it has been addressed on this
forum before (or even hundreds of times before for some issues).
Use the forum's search feature first to see if there are already some good threads on the subject. It's easy to search - just click the "Search" button at the top right of the page.
I cannot stress this enough. We cannot possibly help you if you simply post a thread, copy and paste your whole script and say "it has errors what's wrong with it?". Keep this in mind:
1. Explain to us what your script DOES (or what it's supposed to do).
2. Explain to us what exactly the error is. Is it a PHP error? Your own error reporting? MySQL error? Or is it just not doing what you want?
3. Remember that you know a lot more about your script than we do. Don't assume we know just what it does.
Don't use stupid topic names
Post a descriptive topic name! Give a short summary of your problem IN THE SUBJECT. Don't use attention getting subjects. They don't get attention. They repel attention and annoy people.
Here's a great list of topic subjects YOU SHOULD NOT POST by freebsd:
1) Help me
3) You must know the answer
4) Please help this female newbie
5) Something wrong
6) Come on PHP gurus
7) This one for you
8) Just wondering
9) This is too complicated for me
11) Very urgent
12) I have a question
13) Stupid question
14) Newbie needs help
15) pulling my hair out
16) this is driving me nuts
Generally ANYTHING similar to those is unacceptable. Just post your problem.
Here is a good example of a way to post a question about ereg() and regular expressions / validating emails
"Need ereg regular expression help"
or even better:
"validating emails w/ ereg() regular expressions"
These are bad examples:
"I can't figure this out!"
"Female newbie needs regex help"
"Help me! Urgent!"
ONLY POST THE PART OF YOUR SCRIPT THAT HAS PROBLEMS!
PLEASE do not post your entire script in a message. And if you have to use 2 messages that's a good indication that you're going to annoy people. Only post the part of your script where you have problems. That's it. Just a very small piece of it. It's not hard. Just find the part you think doesn't work and post that. WE DON'T WANT TO SEE YOUR ENTIRE SCRIPT. And if you post the entire script it's going to take us a lot longer to find the problem.
PUT YOUR CODE IN in php vB code!!!
Hundreds of times per week we see people post a huge ugly script right into the message. There's a problem with that. The tabs don't work. There's no syntax highlighting. That makes it difficult to read!
There's a really neat vB code built in that will format and syntax highlight your PHP code when you post it. You can use that easy PHP button right above the box where you type your message. The result will look like this:
If you get an error on a certain LINE, tell us what's on that line and what's on the few lines above it!
// this is some easy to read PHP code
It's not too helpful when you mention an error on a certain line but don't tell us what code is on that line. Because errors can sometimes be caused by lines of code above the one the error is mentioned on, please post a few lines above that line.
Only you know what "doesn't work" means
Please tell us what your script is supposed to do and why it "doesn't work". Or if you don't feel like explaining what the whole script is, at least tell us what the offending code is supposed to do. When you come in and say "it doesn't work" or just "it has errors", that means NOTHING. There could be a million things wrong and no one will know where to look.
If you're not going to take the advice, don't ask for help.
Often times, people post questions about their script with the wrong mindset from the very beginning. Soon they are receiving replies, and silently debugging their code, making no effort to even acknowledge the people helping them! It becomes one sided, and the poster isn't aware that many of the people helping them hope to learn something as well! Letting people know of your progress and how their suggestions apply (or do not apply) will not only help you figure out your problem quicker, but you'll be returning the favor to those of us who learn more by helping.
In even worse scenarios, sometimes the poster will argue back even when they don't know what they're talking about. Hey - if you know it all, don't ask for help.
When people give you free code that may solve your problem, by all means, try it out! And if it's not what you need, at least thank them.
And if people post code that is over your head, ask them for an explanation. Too many times I see great solutions posted, then the original poster doesn't understand it and goes hunting around the PHP manual and finds some function they think will solve their problem but really has Nothing to do with their problem! The solution you are given may not always be something you are totally familiar with, so just ask for a better explanation!
Remember when people help you, they are doing YOU a favor
Regardless of how big your ego is, it is NOT someone else's privilege to debug Your code. It is not their privilege to have them help you. It is YOURS. Remember that when people help you they are doing YOU a favor. You are not doing them a favor by letting them see your incredible application. Be patient, help people out by posting good descriptions of what you need help with, and not snapping at people with garbage such as "if you aren't going to help don't waste my time replying".
Comments on this post
Last edited by Scorpions4ever; February 11th, 2009 at 03:02 PM.
January 7th, 2002, 09:46 PM
June 28th, 2003, 07:54 AM
If you would like to add anything to this thread PM with a request. As Andreas stated, this thread is dedicated to rules/guidelines for posting to this forum.
December 8th, 2004, 08:14 AM
*Submitted my mikateet*
For best results, before posting please attempt to replicate your problem in the minimum amount of code (ideally a single file no more than a 50 lines) and post the entire thing (being sure to use ‘code’ or ‘php’ tags). It is quite likely that during the process of stripping the offending lines of code into the very simple, few line, stand-alone console based (wherever applicable) program that you discover the problem yourself saving everyone time and energy. Do not post executables, it is very unlikely that anyone will ever run them. If you choose to post an entire project for some reason, zip up the directory that contains your code and attach it to a post. Be sure to delete any object files (and executables) as well as any extraneous files; for you VC++ users, delete the Debug and/or Release directories as well as the .ncb file. However, if your program depends on data files, be sure to include a representative sample of the data (but generally no more than a couple of hundred records!). The easier you make it for someone here to replicate your problem (don’t forget to clearly identify the problem (with line numbers!) as mentioned above) the more likely you will receive timely and useful replies.
April 6th, 2007, 01:36 AM
Glossary of BBCode Commands
Just in case, you're wondering how people post bold text or italics text.
You will also find that:
produces better responses.
posting your code within code tags
Up the Irons
What Would Jimi Do? Smash amps. Burn guitar. Take the groupies home.
"Death Before Dishonour, my Friends!!" - Bruce D ickinson, Iron Maiden Aug 20, 2005 @ OzzFest
Down with Sharon Osbourne
"I wouldn't hire a butcher to fix my car. I also wouldn't hire a marketing firm to build my website." - Nilpo