Channel rules
From Cppwiki
Contents |
Asking Questions
Read the appropriate documentation or FAQ before asking
Many questions can be answered by reading some documentation or FAQ material. Microsoft-related questions (especially those involving the Win32 API) can often be answered by reading the appropriate MSDN section at the MSDN website. C++ related questions can often be answered by either Marshall Cline's C++ FAQ Lite or the C++ FAQ.
For examples of MFC and Win32 code, you can also try Code Project and Code Guru.
For a STL/Standard Library reference, take a look at the Dinkum C++ Library site, the SGI STL Programmer's Guide, or the CPPReference.com STL Reference.
Read the pages of this site to see if your question has already been answered
Many topics are covered. Visit the Main Page to start.
Try to ask your question directly, without any unnecessary preamble
Many questions on #C++ begin with "Has anyone ever used X," or "Can someone help me with Y." If someone feels inclined to help, they then invariably ask "yes, what is the problem," and typically get the reply "it doesn't work." Try to be direct and descriptive with your problem, and ask it directly. For example, "When using libFoo for Widget processing, the call to createWidget is failing, but getWidgetError() returns 0. This only happens in release mode, but works fine in debug mode" gives the channel a lot more to go on than simply saying "I can't get libFoo to work."
Saying "it doesn't work" is not a good problem description
This is related to the item above. Obviously it doesn't work, which is why you have a question. When asking a question, try to provide what exactly is not working, and what you've tried to get it to work. For example, if cin is always skipping over a character in your input, don't just say "I can't get cin to work," but rather say something like "cin does not read the last character in my input. I checked the status of the input stream and failbit is not set. The character that is not being read is an ASCII newline character."
Miscellaneous
Do not be excessively annoying. Do not be excessively annoyed
Basically, standard netiquette. Lurk for a few minutes before putting your foot into anything. Learn from your own mistakes and from others.
Do not piss off the ops
This is one of the previously unwritten rules, but here it is laid down as explicitly as possible. While it is not easy to know what will or will not piss off an op, failure to observe the established guidelines on any given channel is a recipe for getting kicked, and #C++ is no exception.
Do not automatically rejoin when kicked
This should go without saying, but if you were kicked from the channel, it was for a reason. If your client is set to rejoin when kicked, then you can't have read the kick reason before rejoining.
Do not ask for pirated software ("warez") or information on illegal activities
Moral and legal issues aside, this is still off-topic and inappropriate for #C++, so don't do it. Ever. If you do, you will be called names, kicked, beaten, drawn, halved and quartered while the ops decide what to do with you.
In other words, no requests for hacks, cracks, keys, serial numbers, or other illegal material will be allowed, and will result in an immediate ban. Do not try to request any file listings or DCCs of illegal files. X-DCC bots are not allowed on #c++.
If we see you typing "!list" or "!files" or any other warez-bot trigger strings, you will be banned.
Do not be obnoxious or offensive
The channel does not tolerate overtly offensive, racist, sexist, or otherwise harmful or hateful speech about anyone. It is one thing to poke fun or make jokes or be politically incorrect, but it is quite another to directly abuse a person or group of people, and doing the latter will earn you a ban from #C++.
If in doubt, tone it down. It's generally ok to make a politically incorrect joke or use a stereotype sarcastically. What's not ok is to direct abuse or offensive speech toward an individual or a group of people based on things like gender, race, sexual orientation, etc.
