Menu
Should be pretty self-explanatory, but this is in the context of real-time XNA code where I want to avoid allocations in order to avoid triggering GC. So I'm wondering if the managed Type objects associated with the types that have been loaded are always present in the runtime, or if typeof() actually constructs a new Type object (presumably from some unmanaged metadata in the runtime) on the heap, which will be garbage collected. Feel free to point out any ignorant assumptions/misconceptions revealed by even asking this question as well =)
301
The typeof keyword is a new extension to the C language. The Oracle Developer Studio C compiler accepts constructs with typeof wherever a typedef name is accepted, including the following syntactic categories: Declarations. Parameter type lists and return types in a function declarator.
The typeof operator is used to get the data type (returns a string) of its operand. The operand can be either a literal or a data structure such as a variable, a function, or an object. The operator returns the data type.
typeof is generally always guaranteed to return a string for any operand it is supplied with. Even with undeclared identifiers, typeof will return "undefined" instead of throwing an error.
Typeof in JavaScript is an operator used for type checking and returns the data type of the operand passed to it. The operand can be any variable, function, or object whose type you want to find out using the typeof operator.
From the C# 4 spec section 7.6.11:
There is only one
System.Typeobject for any given type. This means that for a typeT,typeof(T) == typeof(T)is always true.
(Additionally, if you get the type via reflection it will always fetch the same Type object too, but that's not in the spec.)
78
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
