[dba-Tech] On Odious Code

Think about it...

If something is not nothing, how many other possibilities are there?  Heaps.


Do you think its more efficient to test for each of these other
possibilities?

-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com] 
Sent: Tuesday, 3 August 2004 7:49 PM
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

IMPORTANT - PLEASE READ ******************** 
This email and any files transmitted with it are confidential and may 
contain information protected by law from disclosure. 
If you have received this message in error, please notify the sender 
immediately and delete this email from your system. 
No warranty is given that this email or files, if attached to this 
email, are free from computer viruses or other defects. They 
are provided on the basis the user assumes all responsibility for 
loss, damage or consequence resulting directly or indirectly from 
their use, whether caused by the negligence of the sender or not.