This one again - when comparison attacks!
-
Setup: This is part of a routine to retrieve a string representation of a value via reflection, with certain conditions as to which types and values are allowable.
objValuewill usually be a boxed value type - for instance, aDoublevalue such as0.0... which should result in something like"0"being returned. Really simple stuff... so long as you aren't writing VB while thinking C#.If (Nothing = objValue) Then Return ""
:doh:
----
...the wind blows over it and it is gone, and its place remembers it no more...
-
Setup: This is part of a routine to retrieve a string representation of a value via reflection, with certain conditions as to which types and values are allowable.
objValuewill usually be a boxed value type - for instance, aDoublevalue such as0.0... which should result in something like"0"being returned. Really simple stuff... so long as you aren't writing VB while thinking C#.If (Nothing = objValue) Then Return ""
:doh:
----
...the wind blows over it and it is gone, and its place remembers it no more...
Shog9 wrote:
writing VB while thinking C#.
There you have it in a nutshell; VB. You know that the thinking one is C#, yet you insist on doing this VB stuff. Go and stand in the corner for 10 minutes (act ashamed while you're there).
Deja View - the feeling that you've seen this post before.