performance of typeof()

[pn]

Hi

when comparing a Type object to several built-in types, do you recommend to use Type.GetTypeCode() instead of typeof() ? Is there a BIG performance difference

Example
if (type == typeof(int) || type == typeof(long) || type == typeof(decimal)) ..
-OR
int typeCode = Type.GetTypeCode(type)
if (typeCode == TypeCode.Int32 || typeCode == TypeCode.Int64 || typeCode == TypeCode.Decimal) ..

Thanks for your answers
pn

[Jon Skeet [C# MVP]]

pn <an*******@discussions.microsoft.com> wrote:

when comparing a Type object to several built-in types, do you
recommend to use Type.GetTypeCode() instead of typeof() ? Is there a
BIG performance difference?

Example:
if (type == typeof(int) || type == typeof(long) || type ==
typeof(decimal)) ...
-OR-
int typeCode = Type.GetTypeCode(type);
if (typeCode == TypeCode.Int32 || typeCode == TypeCode.Int64 ||
typeCode == TypeCode.Decimal) ...

typeof is pretty fast, but using GetTypeCode allows you to write it
rather more cleanly:

switch (Type.GetTypeCode(type))
{
case TypeCode.Int32:
case TypeCode.Int64:
case TypeCode.Decimal:

}

That may well be more efficient, too.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[n!]

> typeof is pretty fast, but using GetTypeCode allows you to write it

rather more cleanly:

..........

That may well be more efficient, too.

I assumed typeof() was evaluated at compile-time to become a direct
reference to the Type within the MSIL?

Unless you were referring to the switch() example reducing the number of
comparisons performed in the original example, depending on the actual type
(certainly, I'd prefer the switch you present over the original if
statement).

n!

[Jon Skeet [C# MVP]]

n! <nf********@nomailplease.com> wrote:

typeof is pretty fast, but using GetTypeCode allows you to write it
rather more cleanly:

..........

That may well be more efficient, too.
I assumed typeof() was evaluated at compile-time to become a direct
reference to the Type within the MSIL?

Yes, something like that.
Unless you were referring to the switch() example reducing the number of
comparisons performed in the original example, depending on the actual type
(certainly, I'd prefer the switch you present over the original if
statement).

That's exactly it - a switch statement can (sometimes, not always) be
performed in a very efficient way. Using typeof doesn't allow that
efficiency - you'd have to compare the type in question with each of
the type references.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

pn <an*******@discussions.microsoft.com> wrote:

Thanks for the quick answers! Switch statements aren't appropriate
in my case. To give you a concrete example:

TypeCode type1Code = Type.GetTypeCode(type1);
TypeCode type2Code = Type.GetTypeCode(type2);

if (type1Code == TypeCode.SByte
&& (type2Code == TypeCode.Byte
|| type2Code == TypeCode.UInt16
|| type2Code == TypeCode.UInt32
|| type2Code == TypeCode.UInt64
)
)
return -1;

Would you rather use GetTypeCode() or typeof() here?

I'd use typeof, personally - I think it makes it more obvious what's
going on.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too