[5] Netiquette when posting to comp.lang.c++
(Part of C++ FAQ Lite, Copyright © 1991-2001, Marshall Cline, cline@parashift.com)

FAQs in section [5]:

• [5.1] What does IMHO mean? (or IMO, IMNSHO, FWIW, OTOH, etc.)?
• [5.2] How do I get other people to do my homework problem for me?
• [5.3] What should I do if I see someone else posting a homework problem?
• [5.4] How can I find out about general netiquette so I don't embarrass myself?
• [5.5] What do I do if someone else posts a question that's already in the FAQ?
• [5.6] What makes a good Subject: line?
• [5.7] How do I post a question about code that doesn't work correctly?
• [5.8] Which newsgroup should I post my questions?
• [5.9] Should I post job advertisements and/or resumes on comp.lang.c++?
• [5.10] What if I really need a job; should I post my resume on comp.lang.c++?
• [5.11] What should I do to someone who posts something off-topic?
• [5.12] What about spam?
• [5.13] How do I get the FAQs for a particular newsgroup?

Here's a partial list of acronyms in alphabetical order:

• AFAICS = As far as I can see
• BTW = By the way
• FWIW = For what it's worth
• FYI = For your information
• IMHO = In my humble opinion (egoless)
• IMAO = In my arrogant opinion (a lot of ego)
• IMNSHO = In my not-so humble opinion (a lot of ego)
• IMO = In my opinion (a little ego)
• KUTGW = Keep Up The Good Work
• MYOB = Mind your own business
• OTOH = On the other hand
• RTFM = Read the ___ manual
• SO = Significant other (as in, "My SO and I went for a walk...")

BTW my SO says, "FWIW IMNSHO 'KUTGW' is rare; OTOH it may be helpful to somebody."

For more acronyms please see www.astro.umd.edu/~marshall/abbrev.html.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Shame on you!

Please do not post your homework questions to comp.lang.c++. And don't send them to people via email either!

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

When a slackard asks comp.lang.c++ to do their homework for them, answering their question is the worst thing for them. Please don't do it! Instead you can use the following table of "frequently asked homework assignments" to give them a hint/pointer:

[If anyone has other suggestions that should go into this table, please let me know; thanks; (cline@parashift.com)].

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Key guidelines:

• Do not say, "Please respond by e-mail because I don't normally read this newsgroup". If you don't have enough time for the newsgroup, don't expect the newsgroup to have enough time for you.
• Do not post questions that are answered in the newsgroup's FAQ. That's like saying your time (to read the FAQ) is more valuable than the time of hundreds and hundreds of others (to answer your question). Tres uncool. Read the FAQ first!
• Do not cross post your question to a big pile of newsgroups. Post to the newsgroup (singular) that best fits your question. If you don't get an answer in the "right" newsgroup, post somewhere else but redirect followups back to the "right" newsgroup.
• Do include a working e-mail address in your signature. If your From: address is not correct, please notify your system administrator. Until it's fixed, add a Reply-To: line that gives your correct e-mail address.

Many more general netiquette questions are answered in the newsgroup news.announce.newusers. This newsgroup contains many must-read articles for new users.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Please don't answer a question that's already in the FAQ. Instead politely but firmly point the questioner to the FAQ using the following template:

Subject: It's in the FAQ (was: Original_Subject_Goes_Here)

> Original_Question_Goes_Here [...]

This issue is covered in the C++ FAQ.
You can get the FAQ at:
    http://www.parashift.com/c++-faq-lite/

Please read the FAQ.

If you're willing to help in this effort, consider yourself "deputized" to point people to the FAQ using something like the above template. With your help, hopefully we can improve the signal-to-noise ratio on comp.lang.c++ and thereby preserve it as a valuable resource.

Note #1: Please don't give them the location of the appropriate FAQ. E.g., don't say, "Look at FAQ [10.3]" or "Look in section [10]". It's the old give-them-a-fish vs. teach-them-to-fish problem.

Note #2: Please be polite. I'm hoping we can avoid "RTFM" or "RTFFAQ" euphemisms (or worse!).

Thanks for any help you can give in this matter.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Be descriptive:

• Bad: "Subject: HELP"
• Bad: "Subject: C++ problem"
• Bad: "Subject: SEX SEX SEX"
• Good: "Subject: Problem new'ing a multi-dimensional array"

Mention your compiler/version if you think it's relevant.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Key guidelines:

1. Post compile'able code: avoid ellipses, such as void f() { ... }
2. Post complete code: put in all necessary #includes and declarations of needed types and functions
3. Post minimal code: just enough to demonstrate the problem; skip I/O and calls to libraries if possible
4. Post one compilation unit: if possible, combine Foo.h into Foo.cpp
5. Post the tools you used: compiler name, version number, operating system, etc
6. Post the tool options you used: libraries, exact compiler and linker options, etc
7. Post the exact messages you received; differentiate between compiler, linker, and runtime messages

As always, make sure your question isn't already in the FAQ. Use the subject index to check.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Only post to comp.lang.c++ if your question is about the C++ language itself. For example, C++ code design, syntax, style, rules, bugs, etc. Operating-specific questions (e.g., about Windows NT / 95 / 3.x, UNIX, etc.) should go to an operating-system-specific newsgroup (see below), not to comp.lang.c++.

Here are some other potentially relevant newsgroups:

• comp.lang.c++.moderated
  • A moderated variant of comp.lang.c++
  • The moderator's job is to keep the signal-to-noise ratio higher than in comp.lang.c++
• comp.object
  • Mostly OO design issues, with less emphasis on OO programming)
  • That group's FAQ contains an excellent introduction to OO along with an overview of OO terms and concepts
• comp.std.c++
  • Discussion directly related to the evolving ANSI/ISO C++ standard
  • The evolving ANSI/ISO C++ standard is discussed below
• comp.os.ms-windows.programmer.tools.*
  • This group is intended for discussions about the selection and use of tools for Windows software development
• comp.os.ms-windows.programmer.misc
  • This group is for all other discussions about Windows software development
  • There's one FAQ list for all the comp.os.ms-windows.programmer.* groups
  • Sample topic: Accessing C++ classes in a DLL
  • Sample topic: A dialog as an MDI child window [with OWL]
  • Sample topic: Disabled menu choices become enabled [with MFC]
  • Sample topic: Using STRICT with windows.h
  • Sample topic: A programmer's bibliography
• comp.os.msdos.programmer
  • Much of the traffic is about language products, chiefly from Borland and Microsoft
  • Note: The FAQ for this group is not available at rtfm.mit.edu; it is at ftp://oak.oakland.edu/pub/msdos/info and ftp://garbo.uwasa.fi/pc/doc-net
  • Sample topic: How can I read a character without [waiting for] the Enter key?
  • Sample topic: How can I read, create, change, or delete the volume label?
  • Sample topic: How do I configure a COM port and use it to transmit data?
  • Sample topic: How can a C program send control codes to my printer?
  • Sample topic: How can I find the Microsoft mouse position and button status?
  • Sample topic: How can I write a TSR (terminate-stay-resident) utility?
  • Sample topic: How can I contact [Borland, Microsoft]?
• comp.os.msdos.programmer.turbovision
  • Borland's character-mode framework
• comp.unix.programmer
  • Sample topic: How do I use popen() to open a process for reading and writing?
  • Sample topic: How do I sleep() in a C program for less than one second?
• comp.unix.solaris
  • Covers SunOS 4.x and Solaris
  • Sample topic: Signal Primer
  • Sample topic: Waiting for Children to Exit
• gnu.g++.help
  • Sample topic: Where can I find a demangler?
  • Sample topic: Getting gcc/g++ binaries for Solaris 2.x
  • Sample topic: What documentation exists for g++ 2.x?
• comp.sys.mac.programmer.* and comp.sys.mac.oop.*
  • Macintosh issues
• gnu.g++.bug
  • Bug reports for g++; see the g++ docs
• comp.lang.c
  • FAQ is posted monthly, and is maintained by Steve Summit
  • Sample topic: I'm confused. NULL is guaranteed to be 0, but the null pointer is not?
  • Sample topic: So what is meant by the "equivalence of pointers and arrays" in C?
  • Sample topic: Why doesn't printf("%d\n", i++ * i++); work?
  • Sample topic: How can I write a function that takes a variable number of arguments? [stdarg.h or varargs.h]
  • Sample topic: How do I declare an array of pointers to functions returning pointers to functions returning pointers to characters?
• comp.graphics
  • Issues revolving around graphics programming
• comp.sources.wanted
  • If you want some source code for something, post your request there
• comp.programming
  • General programming issues

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

NO!!!

Job ads, off-topic in comp.lang.c++, give the impression of an employer that is irresponsible and/or technically clueless — not the impression you want to make! Instead post this sort of thing in one of the dozens of *.jobs.* newsgroups that are designed for that purpose.

Note: if you see someone else posting a job ad, please check here before flaming them.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

NO!!!

Resume postings, off-topic in comp.lang.c++, give the impression of an employee that is irresponsible and/or technically clueless — not the impression you want to make! Instead post this sort of thing in one of the newsgroups that are designed for that purpose.

Note: if you see someone else posting a resume or job request, please check here before flaming them.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

An extended flame war against an off-topic posting is just as off-topic as the original off-topic posting. The cure can be worse than the disease.

Instead use something brief and professional such as in the previous two FAQs (which, by the way, were adapted from other sources; see the credits in those FAQs). And please don't get personal or nasty — that just prolongs the (off-topic) exchange.

Remember the 5 "B"s of correction: Be Brief Brother, Be Brief.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Before you throw the word "spam" around (and especially before you acuse someone else of posting "spam"), please check to see some sites that provide a clear definition of exactly when a posting is or is not "spam." One such definition is provided here.

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

Let me count the ways...

FAQs (Frequently Asked Questions lists) are available 24-hours a day via:

• The web: www.faqs.org/
• ftp: ftp://rtfm.mit.edu/pub/usenet/
• e-mail: send a message with the line "help" to mail-server@rtfm.mit.edu
• usenet: many FAQs are available in the newsgroup news.answers

Please, PLEASE do not send e-mail to me!

[ Top | Bottom | Previous section | Next section | Search the FAQ ]

 E-mail the author
[ C++ FAQ Lite | Table of contents | Subject index | About the author | © | Download your own copy ]
Revised Aug 15, 2001