Etienne <etienne.lebeau (AT) matrox (DOT) com> wrote:
Hmm. Interesting. It's worth noting here that *most* of the time is
actually spent in Equals itself. The difference in performance between
the two (at least on my box) is very small compared with the total
time. I would be surprised to see a real-life app where it actually
made a significant difference.

However, I'm still surprised to see "is then as" beating "as then
nullity" in the first place. Hmm.

--
Jon Skeet - <skeet (AT) pobox (DOT) com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

Hi,
I finally found why I was having those strange results. I had to do
with the fact that the method # 2 is using the != operator overload
which is implemented using the Equals()...
Casting to (object) before the nullity check give good results. Thank
you all for this discussion, it was quite interesting.
Best Regards,

Etienne Lebeau, ing. jr.
Software Designer
Matrox Graphics

Etienne <etienne.lebeau (AT) matrox (DOT) com> wrote:
Oh of course - doh! Sorry for not spotting that before.

--
Jon Skeet - <skeet (AT) pobox (DOT) com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too