Comments on: Can I Use Typedef’s in C#?

By: gregd1024

gregd1024 — Sat, 13 Mar 2010 20:53:34 +0000

A short variable in C is the same size as in C# (both take two bytes).

-Greg Dolley

By: Su2anna

Su2anna — Thu, 24 Dec 2009 20:47:50 +0000

does it mean like this

in C

short x;// takes 2 Byte

when i use x in C#

short x;// takes 2 Byte

…………………………….???

By: gregd1024

gregd1024 — Thu, 24 Dec 2009 05:19:11 +0000

Yes, a C++ “short” is an Int16 in C#.

-Greg Dolley

By: Su2anna

Su2anna — Wed, 23 Dec 2009 19:31:22 +0000

what is short equivalent in c#..???

(c/c++–>>short) == (c#–>System.Int16):?

By: BrianMackey.NET » typedef in C#

BrianMackey.NET » typedef in C# — Mon, 21 Dec 2009 23:03:59 +0000

[...] be used to create an alias for a type which appears to be a pretty cool replacement for typedef, this article brings out some interesting and important differences. Mainly, the need to define the alias in [...]

By: CVA

CVA — Fri, 07 Aug 2009 08:05:40 +0000

“[typedefs] not only unnecessarily obfuscates code, it can also cause programmers to accidentally misuse large structures thinking them to be simple types”

The stated intent is to “is to make it easier for programmers to comprehend source code”.
=====================================================================================================

Typedefs are actually meant to support one of the most important principles of programming: “Single Point Control”.

If GLenum one day should be ulong instead of uint it would (if used correctly) only require change to one file.

By: bobobobo

bobobobo — Sat, 13 Jun 2009 12:53:36 +0000

Well, you can shorten float by using

using GLfloat = System.Single ; // typeof(System.Single) == typeof(float)

Also, if you wanted to bring an enumerated type into C# from somewhere else, you’d better do something like

public enum GLenum : uint
{
// list values
}

Which says that GLenum’s underlying type is unsigned int

By: ac

ac — Mon, 21 Jul 2008 13:47:17 +0000

linux kernel developer: (http://en.wikipedia.org/wiki/Typedef)

“[typedefs] not only unnecessarily obfuscates code, it can also cause programmers to accidentally misuse large structures thinking them to be simple types”

The stated intent is to “is to make it easier for programmers to comprehend source code”.

I’ve done some C/C++ porting but my background is C#. There is little doubt in my mind that typedefs made the code harder to understand when I needed to.

You don’t say why would you want to have this feature in C#? It could make it easier for porting legacy code to C#. So now you have some obfuscated C# … Now we might give C# all the goodies from C++ and then call it C++/CLI but would we prefer using this language over C#? I think you’ll find more C++ devs who like C# than C++/CLI if you asked around.