No typedef in C# 2.0

Long Gone

Matt Gerrans wrote: Wouldn't it be C++++ in that case? Only if you write C## Don't shoot! I'm only the piano player messenger. Beatress

Matt Gerrans

Look more closely. Matt Gerrans

Rei Miyasaka

Remember in the Windows API how when you hunt through the jumble of typedefs and #defines, ints and HANDLEs and DWORDs and FAR and a bunch of other stuff turn to be the same thing? Or how MessageBox() and MessageBoxA() and _MessageBox() and __MessageBox() were all the same thing? I think the goal is to discourage that sort of thing. It'd be easy to use but it'd also be easier to abuse. Integrity is a key design objective in .NET.

Paul Selormey

typedef will be misleading. Anytime you do List<int> in C++, the compiler generates a class for you at compile time. The typedef in C++ is simply doing what the compiler will be doing anyway, but giving the generated class of the type List<int> a name you can remember. The Generics is designed to avoid the compile time class emitting, so throwing in a typedef will give a wrong image. This my understanding of the Generics concept and why it is maintained like that in MC++/CLR-C++ along side templates. Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.

Long Gone

Matt Newman wrote: I thought the # was just a cool way of drawing two +'s # => ++ so ## => ++++ Matt Gerrans wrote: Look more closely. Obviously I am missing something. P.S. – for all you anal retentive folks out there tempted to comment on my spelling or grammar save your energy. I don’t care. Don't shoot! I'm only the piano player messenger. Beatress

Vagif Abilov

Agree. How many various 32-bit types will we find in Win SDK headers. I guess several hundred. Вагиф Абилов MCP (Visual C++) Oslo, Norway If you're in a war, instead of throwing a hand grenade at the enemy, throw one of those small pumpkins. Maybe it'll make everyone think how stupid war is, and while they are thinking, you can throw a real grenade at them. Jack Handey.

Matt Gerrans

Obviously:

# == ++ == ++++
++

QED ;P Matt Gerrans

Rei Miyasaka

Or you can take 2 +s, extend the lines and arrange them diagonally:

| | | |
-+--- | -+--+-
| + | = | |
| ---+- -+--+-
| | | |

Matt Gerrans

Two distorted +'s perhaps. Matt Gerrans

Rei Miyasaka

:)

Giles

I could see how that would be very useful, and help clean up code readability. Something I take for granted in C++, and don't think about. Personally, I would quite like a preprocessor as well.

Emilio Garavaglia

"Interity" or "Integralism"? What's the matter with a type name redefinition for my own use, if it is closed in my own namespace? The (ab)use of type redefinition in Win32 derived from the fact that it was designed in flat namespace environment (plain C). All the consideration about templates and generics are correct, but the idea to alias a frequently used name dosn't semm to me so peregrine. My opinion is that ... they simply forgot it. And we are trying to justify them by "inventing" forcing anyone to use "patterns" also when not the case. And calling this "intrgrity". Did The "goto" history, blamed by zealots and rewed recently, teach anything ?? 2 bugs found. > recompile ... 65534 bugs found. :doh:

Long Gone

Good one!:) P.S. – for all you anal retentive folks out there tempted to comment on my spelling or grammar save your energy. I don’t care. Don't shoot! I'm only the piano player messenger. Beatress

Jorgen Sigvardsson

The thing is though that we ain't supposed to know that they're 32 bits wide.. ;P Good music: In my rosary[^]

Daniel Grunwald

It's called using, not typedef: using StringPair = System.Collections.Generic.KeyValuePair<string, string>;

Alvaro Mendez

I know about using, but it's only available for the current file. It would need to be repeated in every file you'd want to use StringPair. using is just an alias; it doesn't define a distinct type like typedef does (in C++). Regards, Alvaro

Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is. -- GWB, 1999.