I think the start is wrong... we can pass types as parameters.
A method like this:
void ShowName(Type type)
{
Console.WriteLine(type.FullName);
}
can be called as:
ShowName(typeof(object));
or as this:
ShowName(someObject.GetType());
If you are trying to say that we can't pass
enum types as type parameters, I will partially agree, as we can't use
where T: enum. But, you say that generic methods solve the problem, so that's not the case.
The only advantage (if that's really to be considered one) about using generic methods to pass types is that
null or open generic types (like
List<> without specifying a data type) will never be received. But doing the necessary
ifs are probably faster than counting with the generation of the method.
I started to program computers when I was 11 years old, as a hobbyist, programming in AMOS Basic and Blitz Basic for Amiga.
At 12 I had my first try with assembler, but it was too difficult at the time. Then, in the same year, I learned C and, after learning C, I was finally able to learn assembler (for Motorola 680x0).
Not sure, but probably between 12 and 13, I started to learn C++. I always programmed "in an object oriented way", but using function pointers instead of virtual methods.
At 15 I started to learn Pascal at school and to use Delphi. At 16 I started my first internship (using Delphi). At 18 I started to work professionally using C++ and since then I've developed my programming skills as a professional developer in C++ and C#, generally creating libraries that help other developers do their work easier, faster and with less errors.
Want more info or simply want to contact me?
Take a look at:
http://paulozemek.azurewebsites.net/
Or e-mail me at: paulozemek@outlook.com
Codeproject MVP 2012, 2015 & 2016
Microsoft MVP 2013-2014 (in October 2014 I started working at Microsoft, so I can't be a Microsoft MVP anymore).
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
