typeof(string)? Meh.

[PIEBALDconsult]

It's a win/win/win.

[Andy Brummer]

dnh wrote:

typeof shows intention much better (and is shorter), it's also faster. Excellent.

Hey, what if I want potential runtime errors? You just need to write a unit test to make sure column.DataType == typeof(string).

---

I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon

[PaulPrice]

I dont get the question, call me stupid if you will!

[DavidNohejl]

column.DataType = System.Type.GetType("System.String"); column.DataType = typeof(string); Second line is more readable (IMO), less typing, and faster. There is absolutely no sane reason to write it the first way, hence my (not really a) question. :)

---

[My Blog]
"Visual studio desperately needs some performance improvements. It is sometimes almost as slow as eclipse." - Rüdiger Klaehn
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe

[Paul Conrad]

PIEBALDconsult wrote:

It's a win/win/win

And those are very nice situations to be in :rolleyes:

"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus

[Paul Conrad]

It is not really a question, it is a programming horror the OP ran across.

"Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus

[PaulPrice]

ahhha, now I understand

[leppie]

System.String might not be defined in the current scope (reasons why, god knows)! Then typeof() wont work :)

[Vasudevan Deepak Kumar]

GetType() takes more time because of its runtime evaluation right?

Vasudevan Deepak Kumar Personal Homepage Tech Gossips

[Vasudevan Deepak Kumar]

dnh wrote:

less typing, and faster

And relatively less bytes to save on disk and less data to transfer across the wire during FTP and other copy operations. :-D

Vasudevan Deepak Kumar Personal Homepage Tech Gossips

[DavidNohejl]

They are both in run time but there are JIT optimalizations... I've just found more on this topic in this[^] blog post.

---

[My Blog]
"Visual studio desperately needs some performance improvements. It is sometimes almost as slow as eclipse." - Rüdiger Klaehn
"Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe

[dojohansen]

I believe the typeof(T) operator is resolved at compile-time. Thus when you speak of how long "typeof took" you are really only measuring the time spent to loop, increment and check loop variable, and perform the assignment. The MSDN documentation does make a distinction between types in general and the type objects that represent types (and which are, of course, themselves types). For example, the reference for the typeof() operator mentions: Used to obtain the System.Type object for a type. A typeof expression takes the following form: System.Type type = typeof(int); It's clear that the System.Type is the "metatype", the type that is created for us but describes a type we created. It also says to use GetType() to obtain the run-time type of an expression (although not the GetType overload discussed here, taking a string and finding a corresponding type in any loaded assembly in the appdomain!), and I take this as evidence in support of the "typeof() is resolved at compile-time" hypothesis. :)