Are there a set order for which specifiers must follow? e.g
consider:
Is the above the same as this:Code:extern const volatile static unsigned long int i;
Code:long extern const static unsigned volatile int i;
Are there a set order for which specifiers must follow? e.g
consider:
Is the above the same as this:Code:extern const volatile static unsigned long int i;
Code:long extern const static unsigned volatile int i;
I AM WINNER!!!1!111oneoneomne
Storage class specifiers (IE extern, static, auto) should be first.
Also, you used both extern AND static, which is not valid.
EDIT: Hm, actually, I'm not sure if storage class specifiers HAVE to be first, but I was told they did a while back, and Comeau in strict mode issues a warning when they are not first.
Still, try to keep the storage class specifiers first.
Last edited by Polymorphic OOP; 01-21-2003 at 07:53 PM.
Thanks for your explanation. Another question, I assume non-global variables are placed on a stack, and that stack is usually the RAM? Im wondering, for big programs like games, where the amount of variables exceed the RAM limits and they have to be stored on the harddisk, would pointers storing addresses of variables stored on a harddisk still work?
I AM WINNER!!!1!111oneoneomne
They just don't load everything in memory at once. Data is dynamically allocated and deallocated on the heap. You don't use the hard drive for variables. You can't have pointers to "variables" on a hard drive.