Re: Generic Delegate Types explained (example)
- From: raylopez99 <raylopez99@xxxxxxxxx>
- Date: Mon, 18 Aug 2008 16:39:58 -0700 (PDT)
On Aug 18, 4:25 pm, "Peter Duniho" <NpOeStPe...@xxxxxxxxxxxxxxxx>
wrote:
On Mon, 18 Aug 2008 11:23:07 -0700, Chris Dunaway <dunaw...@xxxxxxxxx>
wrote:
[...]
Sometimes you have to refute a post, even if you know it will result
in a long discussion like this one. Without some sort of refutation,
those who come here to learn (like me) might get some erroneous
information.
I'm of a mixed mind on the topic. For sure, there is no need to reply
with anything other than "that post was entirely incorrect". An extended
discussion is not necessary.
Your assumption is flawed: that my OP was troll bait. It was not. I
was learning about generic delegate types, and I actually learned a
lot (and so would others) by doing the exercise I posted. A beginner
would learn a lot too. And it's not found in any textbook. Often the
textbooks have a lame example where something, like an int, is being
squared. By contrast, I showed not just an int, but how to write for
an object, even if the delegate template returns "void" and still get
the job done, and, with the help of Marc, how to modify the delegate
template to work. Invaluable, not at all a troll post. But, having
said that, my original (troll) intuition was correct: try and avoid
generic delegates when possible--they just confuse your code.
But beyond that, this is an unmoderated forum and readers _should_ be
taking care to consider the source when reading a post. There is already
ample evidence that Ray doesn't have a clue about C#, and any reader
paying attention should be able to pick up on that easily just by reading
past threads that involve him.
Not true. I have a big clue about C#, and have written useful
programs even last year. this year I'm even more proficient. Again,
you're talking down to me and the reader. You teach perhaps? Sounds
like a junior lecturer at some community college that thinks he knows
it all.
The real problem is that responding to the trolling posts just encourages
the troll. Even if all you say is "that was entirely incorrect", that
provides an opportunity to the troll for him to respond with another
post. People need the intestinal fortitude to just let him post
ridiculous things, and trust that they are so ridiculous that any reader
paying attention will recognize them as ridiculous.
Well, let's see if you practice what you preach--I just left an
innocent comment on your blog about some redundant programming
exercise you wrote on text boxes and reinventing the same--let's see
if you post it.
I agree with you that there is some risk that some people will be misled.
But there's a lot of great content in this newsgroup if you ignore Ray's
additions, and anyone having trouble trying to figure out something Ray
might have suggested can be quickly brough back on track if and when they
post a follow-up question that someone who knows what they're talking
about can help with.
That's assuming people ignore your suggestion that I be boycotted. I
guess you haven't thought that through, kinda like your code. Unless
you suggest people only reply to people replying to my posts. Don't
know how you can configure your .kill file newsreader to do that
without missing the original post and losing context, but I guess it's
possible.
I don't have any solid proof, but it's my belief that the risk to the
quality of the newsgroup related to replying is greater than that related
to not replying. In the long run, I believe we'll be better off not
replying at all.
You seem to contradict your previous paragraph. Guess your state of
mind is unstable?
RL
.
- References:
- Re: Generic Delegate Types explained (example)
- From: raylopez99
- Re: Generic Delegate Types explained (example)
- From: Marc Gravell
- Re: Generic Delegate Types explained (example)
- From: raylopez99
- Re: Generic Delegate Types explained (example)
- From: Jon Skeet [C# MVP]
- Re: Generic Delegate Types explained (example)
- From: raylopez99
- Re: Generic Delegate Types explained (example)
- From: Peter Duniho
- Re: Generic Delegate Types explained (example)
- From: Chris Dunaway
- Re: Generic Delegate Types explained (example)
- From: Peter Duniho
- Re: Generic Delegate Types explained (example)
- Prev by Date: Re: C#--is it growing? Or saturated? (Charles Petzold does C#)
- Next by Date: Re: Populate collection object with field names from SQL table?
- Previous by thread: Re: Generic Delegate Types explained (example)
- Next by thread: Re: Generic Delegate Types explained (example)
- Index(es):
Relevant Pages
|