When should I use:
Int32 myint = 0;//Framework data type
vs
int myint = 0;//C# language data type
What are the similarities/differences? I seem to recall being told that there are performance differences? Is this true?
views:
137answers:
4
+1
A:
Interesting: The compiler doesn’t allow you to type enum using the “Int32” but it does when you use “int”.
lance
2009-07-30 17:37:32
+7
A:
In C# the language-defined keywords for data types are just aliases for their respective BCL types. So int is exactly the same as Int32, long is the same as Int64, etc.
In general I'd think it's best to stick with the language-defined type names, though. There are definitely no performance differences as those aliases are resolved by the compiler.
Joey
2009-07-30 17:41:08
My C# compiler happily recognized `Main` with `System.String[]`. Where did you get this bit from?
Pavel Minaev
2009-07-30 17:42:49
Remember someone having this problem here on SO. Might have been wrong, didn't try. I removed that bit.
Joey
2009-07-30 17:43:25
Visual studio has a problem recognizing Main(String[]) as a valid Main.
Henk Holterman
2009-07-30 17:48:24
Ah, that was it, then.
Joey
2009-07-30 17:55:11
Note, this is not true in some other languages (like Java) where using Integer generates a Boxed reference type.
Nader Shirazie
2009-07-30 20:16:12
nader: The question was about .NET. And the dichotomy of primitives and wrapper classes is usually clear to most people writing Java :)
Joey
2009-07-30 20:54:52
+4
A:
int is an alias for System.Int32, string is an alias for System.String. There are no differences.
That said, it's better practice to use int and string, not their System equivalent, mostly for readability. If you use a source style checker such as StyleCop, it will enforce replacing all System.String and System.Int32 declarations with their shorter equivalent.
Will Eddins
2009-07-30 17:41:24
Since usually all source files have a `using System;` at the top you wouldn't have to qualify the type name with its namespace on each use :)
Joey
2009-07-30 17:45:11
You wouldn't have to due to the using statement, but in the case of int and string, you would never have to.
Will Eddins
2009-07-30 17:46:30
+1
A:
I used to advocate using C# language aliases over CLR types, but I changed my preference to using CLR types after I heard that Jeffery Richter advocates the CLR type in his book CLR via C#, my first hand dealing with other devs new to the CLR, the ability to see that the CLR, instead of C#, is the center of attention, as well as color clues between reference and value types helps in visually parsing code quickly.
codekaizen
2009-07-30 17:46:26