[5.2] How do I get other people to do my homework problem for me?
Shame on you!
Please do not post your homework questions to comp.lang.c++.
And don't send them to people via email either!
"If I did your homework for you, then you might pass your class without
learning how to write a program like this. Then you might graduate and get
your degree without learning how to write a program like this. You might
become a professional programmer without knowing how to write a program like
this. Someday you might work on a project with me without knowing how to
write a program like this. Then I would have to do you serious bodily harm."
[Thanks to Jack Klein]
[5.3] What should I do if I see someone else posting a homework problem?
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 someone asks...
...then here's a brief answer:
How do I do Equation Parsing in C++?
Use a stack of operators to convert infix to postfix, then a stack of operands to evaluate the postfix expression.
How do I do Shortest Path in C++?
Look up Dijkstra's algorithm and backtracking.
How do I do Sorting in C++?
Look up heapsort, quicksort, merge sort, internal and external sorting.
How do I do Minimum Spanning Trees in C++?
Look up Kruskal and/or Prim's algorithm.
How do I do Combinations and/or Permutations in C++?
See your algorithms book.
How do I do <some small essay problem; obviously contrived for a school assignment; too well defined to to be from the real world> in C++?
Do it yourself. If you get stuck, ask a specific question.
[If anyone has other suggestions that should go into this table, please let me
know; thanks; (cline@parashift.com)].
[5.4] How can I find out about general netiquette so I don't embarrass myself?
Guidelines:
Do not say, "Pleaserespondbye-mailbecauseIdon'tnormallyreadthisnewsgroup". 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 not top-post. In other words, don't type your reply
above the previous author's text. Even if top-posting seems "natural" or
"obvious" or "better," don't do it it's not the comp.lang.c++
"way."
Do not post HTML or "rich text." Like it or not,
comp.lang.c++ is a plain-text newsgroup.
Do not post "attachments."
Do not refer to "C/C++." Some people get testy about that,
and will (unfortunately!) ignore everything else you say just to correct you
with something like, "There is no such language." It borders on pathetic, but
you'll probably be okay if you say "C or C++" instead of "C/C++."
Sigh.
Do not confuse a class with an object. E.g., don't say,
"How can I allocate a class?" or "My code creates a class via new." If you
say something like that, at least a few people won't even bother to answer the
question you intended to ask, but will instead use their entire reply simply
to correct the words you used. Sigh (x2).
Many more general netiquette questions are answered in the newsgroup
news.announce.newusers. This newsgroup contains many must-read
articles for new users.
BTW here's a cute joke that tells you how people feel about top-posting (with
credits to "Gordon" on apihna):
A: Top posting!
Q: What is the most irritating thing on Usenet?
[5.5] What do I do if someone else posts a question that's already in 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: 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!).
[5.6] Wait a minute, does that previous FAQ say to not answer their question just because it's already answered in the FAQ?!?
Yes, that's exactly what the previous FAQ says: when someone asks a question
that's already in the FAQ, please do not answer their question.
The poster is better off if you don't answer a
FAQ-question: if you really want to help people, help them
become self sufficient so they're not always dependent on others to look
things up for them.
The newsgroup is better off if you don't answer a
FAQ-question: if you actually answer their question, chances are your
answer will elicit follow-up postings and increase the amount of "noise" on
the newsgroup. This reduces the newsgroup's value to everyone.
People ought to ask others for help with questions that aren't in the
FAQ. But please don't cripple people by training them to depend on others for
answers to questions that are in 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. Ultimately this means your question must be answerable by looking into
the C++ language definition as determined by the ISO/ANSI C++ Standard
document, and by planned extensions and adjustments. 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:
Covers Visual C++ .NET. If it doesn't appear in your news server use the
public MS news server at msnews.microsoft.com. Please do NOT write me
asking how to set up your newsreader.
Usenet isn't the only place that has forums to answer your questions. You
might also try Techi-Warehouse,
among others. Please don't email me asking to add others; I don't have time
(or the interest!) to make this an exhaustive list of forums.
[5.10] Should I post job advertisements and/or resumés on comp.lang.c++?
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 your job ad / resumé on one of the
dozens of *.jobs.* newsgroups that are designed for that purpose.
[Adapted with permission from postings by David Harmon and Brian B. Rodenborn]
[5.11] What if I really need a job; should I post my resumé on comp.lang.c++?
NO!!!
Resumé 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 your job ad / resumé on one of the
newsgroups that are designed for that purpose. [Adapted with permission from
postings by David Harmon and Brian B. Rodenborn]
[5.12] What should I do to someone who posts something off-topic?
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.
Before you throw the word "spam" around (and especially before you
accuse 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.