I always mess up how to use const int *, const int * const, and int * const correctly. The question what is the difference between int* and int []? is a less trivial question than most people will think of: │int││int││int││int││int││int││ └───┘└───┘└───┘└───┘└───┘└───┘└┄ of course, there's no reason they can't all.
A c++ question, i know int* foo (void) foo will return a pointer to int type how about int &foo (void) what does it return? This stems from the c compiler (and it's compatible c like systems) ignoring white space in token stream generated during the process. Is there a set of rules defining what you can and cannot do?
An integer (with capital i) holds a reference to an object of (class) type integer, or to null. It is a pointer to function that returns int* and accepts int* and pointer to function that returns int* (and accepts undefined number of parameters; It depends on where it is used. In c#, int and int32 appear to be the same thing, but i've read a number of times that int is preferred over int32 with no reason given.
Java automatically casts between the two; It will initialise your variable a to the default value of an integer, i.e. An int variable holds a 32 bit signed integer value. I want to know all the do's and all.
Are the two really the same? Int* i, int * i, int*i, and int *i are all exactly equivalent.