Craig,

I've been thinking on your response, and the instructor in me keeps sayin=
g=20
that it's important to teach this philosophy, not give clues to it.

Your reply below would have been the best reply possible.  Not the vague =
hints=20
to what he should have done.  So yes, your intentions were correct, your=20
presentation seemed lacking. =20

I apologize for not thinking through my response to you, it should have b=
een=20
what I wrote above.

anthony


>
> - Don't post homework questins
>
> Before asking a technical question by email, or in a newsgroup, or on a
> website chat board, do the following:
>
>      1. Try to find an answer by searching the Web.
>
>      2. Try to find an answer by reading the manual.
>
>      3. Try to find an answer by reading a FAQ.
>
>      4. Try to find an answer by inspection or experimentation.
>
>      5. Try to find an answer by asking a skilled friend.
>
>      6. If you are a programmer, try to find an answer by reading the
>         source code.
>
>
> When you ask your question, display the fact that you have done these
> things first; this will help establish that you're not being a lazy
> sponge and wasting people's time. Better yet, display what you have
> learned from doing these things. We like answering questions for people
> who have demonstrated that they can learn from the answers.
>