There is a difference. Static variables are initialized in the dynamic memory space and therefore occupy additional memory space not to mention the fact that you need executable code (additional memory) to initialize them and access them.
All const data is located in the same memory space as executable code which is read-only-memory (ROM), where as static data is loaded into dynamic memory where you can potentially read and write to it. Now here is the interesting part that seems to have been overlooked in previous answers. Static data occupies dynamic memory space but requires additional ROM space and, in the worse case scenario, can take up twice the amount of memory. Consider the following:
class StaticData
{
static string s_static1 = "My string data";
}
class ConstData
{
const string CONST1 = "My string data";
}
The class StaticData has variable s_static1 which will occupy dynamic memory space of a single pointer (normally 1 integer). However it also has to be initialized and therefore there must also exist ROM code to initialize it. The string data itself would normally be located in ROM space, since string data is immutable, and would not take up any more space than the constant excample.
For the class ConstData there is only ROM storage space required and therefore this is, in most cases, the best usage of memory.
Now it gets more interesting when you consider how the data is used by the compiler. With the exception of string/character data, constants are normally substituted directly in code at the point of reference. In other words the constant value is directly loaded into a register or pushed onto the stack, depending on usage. In the case of a static variable the compiler has to read that value out of memory via additional code (pointer referencing) and therefore additional ROM code is required.
In summary static code will take up more memory both by occupying additional dynamic memory space and the additional executable code space required to de-referrence it.
