Using Int32 or what you need

Should you use Int32 in places where you know the value is not going to be higher than 32,767?

I'd like to keep memory down, hoever, using casts everywhere just to perform simple arithmetic is getting annoying.

short a = 1;

short result = a + 1; // Error

short result = (short)(a + 1); // works but looks ugly when does lots of times

What would be better for overall a开发者_开发知识库pplication performance?

As far as i know it is a good practice to use int whenever possible. Size of int equals to a word size on many architectures, so i think there may be a slight performance degradation when using short in some arithmetical operations.

If you are creating large arrays, then it can save a considerable amount of memory to use narrower types (less bytes), as the size of the array will be "type width" * "number of elements" + "overhead".

However, I'm pretty sure by default that in classes and structs, they will be packed along whole word boundaries e.g. 32bit = 4bytes. A short will still be packed into a 4 byte space.

You can however, manually configure packing in structs\classes by using structure layout:

http://msdn.microsoft.com/en-us/library/system.runtime.interopservices.structlayoutattribute(VS.71).aspx

As with any performance related issue: "don't think - measure".

From an API perspective, it can be majorly annoying to have to keep casting from shorts to ints, etc, as you will find most APIs will use ints for example.

The 3 reasons for me to use a integer datatype smaller than int32:

1. A system with severe memory constraints.
2. Huge arrays or similar.
3. I think it would make the purpose of the code easier to read and understand.

I mostly do normal Windows apps, so the the only reason of those that normally matters to me is the 3rd one.

Unless you're creating 100s of thousands of members then the space savings of a handful of bytes here and there won't really matter on any modern machine. I think the maxim of premature optimization applies here. It might make you feel better, but you're not getting anything particularly measurable out of it. IMO - only optimize memory usage if you're actually using a lot of memory.