Why we should Use built-in C# native data types vs .NET CTS types ( Use int Not int32, use string not String , use bool not Boolean)

Question

0.00/5 (No votes)

See more:

Posted 19-Mar-12 1:45am

raghubansh kumar

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Answer 1 · 2012-03-19T01:55:00

Solution 2

One of the times you need to use Int32 instead of int would be if you want be double-damn sure that you get a 32-bit int in a 64-bit app (or when reading a data file), or when they redefine int to be equivalent to Int64 instead of Int32. The int used to be the same as Int16.

There are probably other examples, but that's the one that came to mind first.

Posted 19-Mar-12 1:55am

#realJSOP

Comments

Sergey Alexandrovich Kryukov 19-Mar-12 21:05pm

"They" are not really supposed to redefine them... however... who knows?
--SA

#realJSOP 21-Mar-12 6:15am

In VS 1.51, an int was 16-bits. In a later version (I don't know which version this happened), it was made equivalent to an Int32 (but you could still use int as your type definition). At some point, int will be an Int64, probably when/if we ever see 128-bit operating systems.

Sergey Alexandrovich Kryukov 21-Mar-12 21:09pm

I know, I know. I want to emphasize the paradigm shift in .NET: C approach was focus on platform-dependent types, .NET - on platform-independent. You know that for two 64-bit targets int is 32-bit, exactly as in x86. That is the difference. A 128-bit integers will be added without replacing any other existing types.

A point?
--SA

OriginalGriff · Answer 2 · 2012-03-19T01:52:00

Solution 1

o reason, really - it is just tidier.
int is just syntactic sugar for int32,

bool

works the same as Boolean

It just makes the code slightly more readable, and more compatible with (for example) C and C++

If your company rules don't prevent it, you can use whichever you want - just try not to mix them!

Posted 19-Mar-12 1:52am

OriginalGriff

Comments

Sergey Alexandrovich Kryukov 19-Mar-12 21:04pm

Agree, a 5.
Just a note: when we prefer int over System.Int32, we do not choose a type. The type "int" is no more then a C# alias for System.Int32. Same goes for uint, byte, sbyte, string, object, etc.
--SA