[dba-Tech] On Odious Code

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.

Bobby

-----Original Message-----
From: dba-tech-bounces at databaseadvisors.com
[mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Tuesday, August 03, 2004 6:19 AM
To: 'Discussion of Hardware and Software issues'
Subject: [dba-Tech] On Odious Code


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.

A.

_______________________________________________
dba-Tech mailing list
dba-Tech at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-tech
Website: http://www.databaseadvisors.com