Re: Registering Event Handlers in C# vs. VB .NET

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Scott M." <smar@xxxxxxxxxxxxx> wrote in message
news:e7Pv%23ykTIHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
Chris,

That makes no sense. You are saying that the subset Peter describes as
having a problem with understanding events are those who have trouble
understanding events?

No, go read his first post - he clearly says that a VB .NET developer will
have trouble... He does not qualify any subset.

He said "can", a potential, a possibility, not "will". I quote "It can be
an especially difficult leap for a VB.NET programmer to grasp". If, picking
a VB.NET programmer at random, the probability that said programmer has
difficulty grasping the concept is non-zero, then the statement is accurate.
This is both necessary and sufficient assuming that the pool of VB.NET
programmers is finite, which if we discount the possibility of
non-Earthlings somewhere having acquired VB.NET skills, is well founded.

Since we've heard several examples of anecdotal evidence that at least some
VB.NET programmers have been observed to have difficulty with that exact
concept, the statement is accurate.

Now I don't exactly agree with the way Peter sunk to ad-hominem attacks when
his statement was questioned, but I think I've been at least that tactless
at times so I will encourage all to simply forgive.


-Scott

"Chris Shepherd" <chsh@xxxxxxxxxxxxxx> wrote in message
news:ebG5ZkkTIHA.4768@xxxxxxxxxxxxxxxxxxxxxxx
Scott M. wrote:
We're not going to debate what the meaning of "is" is are we?

Without calling my college English professor, I think it's pretty
obvious that your first post was not referring to any specific subset of
VB developers, you wrote "a VB .NET programmer", you did not qualify the
subset to which that programmer belongs in your estimation. Later on,
you said

This is incorrect. Peter did qualify which subset of VB .NET programmer
he was discussing -- those for whom it (proper event handler
registration) was a difficult concept to understand.


Chris.





.

Relevant Pages

  • Re: the free software paradigm
    ... You could start a union to protect programmer wages. ... How could you make trouble to the user? ... And there is nothing software written by non-unionized programmer ...
    (comp.lang.lisp)
  • Re: Conversion of data & associated logic from ISAM to RDB
    ... I have been a programmer since 1965. ... Saturday) to write this response. ... I am getting a bit tired of certain people here ALWAYS seeing the trouble as ... There ARE bad managers, just as there are crap programmers. ...
    (comp.lang.cobol)
  • i have a trouble in inherit value list of access 2007
    ... i am new programmer and use access 2007 to do customed software. ... trouble with a combo box. ... i enable its properties of inherit value list and ...
    (microsoft.public.access.forms)
  • Re: RS232 Level Correction
    ... > a proper programmer design and quit trying to fudge something like Vpp ... casing (nor can you connect an oscilloscope ground) or the whole thing ... trouble reading/verifying the chip, I'd look towards a software error on ... Not to mention that the inputs only want to see 0V and +5V signals. ...
    (sci.electronics.basics)
  • Re: Very brief rant.
    ... abuse@xxxxxxxxxxxxxxxxxxxx (Peter) wrote: ... >> I'd more say "if a programmer asks to borrow any tools of yours, ... >> worry. ...
    (alt.sysadmin.recovery)