Strangely, you seem to be more interested in flames than you are in
programming C#.
Then clearly you're not reading my posts outside this thread.
Plenty of misguided threads are turned into productive
threads by using the question as a jumping off point for discussion of
esoteric or controversial details of the topic.
No doubt - but that doesn't mean that it's a good idea to have those
misguided threads in the first place. Any number of things which are a
bad idea in themselves sometimes lead to good results - that doesn't
mean the original action is any better.
I already explained to you that I did look up "foreach" and I coded it. but
then I received a compile time error I did not understand and, believing
that I had not coded a direct analogy to VB code, I decided to post to the
forum. You are actually reading what I write aren't you ?
Absolutely. However, you didn't explain that you looked it up. You said
that you were using it, but not that you had looked it up. If you
really think that you explained that you'd looked it up, please say
which post you said that in.
Given that if you type in "foreach" in the MSDN index, it gives you a
description of the syntax and lots of examples, it surprises me to hear
that you could have seen those and still asked the question. (And as I
say, a Google search with your subject line gives the information
immediately too.)
In any event, it is my understanding that posters here have neither an
obligation nor a privilege nor a reward to respond to questions, and so I
fail to see why you insist on making such a big deal out of this. There are
thousands and thousands of posts and the vast majority go unread by any
single individual, so what does it matter if someone makes a mistake every
now and then ?
It's a big deal because you don't seem to see a problem wasting
people's time. Even just skipping over a post takes *some* time.
I thought QWERTY's original response was a bit rude, but slightly
deserved. While put a bit strongly, the suggestion that it would have
been better to read the manual (which does make the answer very clear,
IMO) was reasonable.
If you personally owned this newsgroup then it might be another matter, but
you don't.
So does that mean I can't encourage people to ask questions having
looked up documentation? People often ask questions without doing
appropriate research, or without posting nearly enough (or the right)
detail to work out what's gone wrong. The newsgroups would be much more
useful if they did a bit of leg-work first, and I don't see what's
wrong with saying that.