[dba-Tech] On Odious Code

Hi Bobby and Arthur

> I think IsNot is used because it is comparing an object to Nothing and <>
> would not work.

> I myself would prefer Is Not Nothing, but no one asked me.  LOL.

I would have preferred

       If Not m_Enter Is Nothing Then
         m_Enter.Invoke(sender, e)
       End If

Can't see what improvement "IsNot" brings ...

No one asked me.

/gustav


> Does anyone but me find this syntax odious? (Lifted from a .NET example)

>       If m_Enter IsNot Nothing Then
>         m_Enter.Invoke(sender, e)
>       End If

> What is this "IsNot Nothing" crap? Have we descended to those languages in
> which any negative requires a pairing (i.e. as in French, ne <verb> pas)?
> Why not test the positive case instead? I guess my time has past and this
> syntax is now considered kewl. But it makes me hurl, just as "to each their
> own" makes me hurl. I realize that language is a process not a static
> object, but sheesh. "IsNot Nothing"? Come on! Even if we want to preserve
> the negative attitude, can't we substitute "<>" for IsNot?

> I'm beginning to hate where programming is going.