the following code is giving me the error:
syntax error before '.' token
why is it so??Code:struct point zero; zero.location[0]=0; zero.location[1]=0;zero.location[2]=0; zero.coords[0]=0;zero.coords[1]=0;zero.coords[2]=0; zero.p_xyz[0]=NULL;zero.p_xyz[1]=NULL;zero.p_xyz[2]=NULL; zero.p_xyz_n[0]=NULL;zero.p_xyz_n[1]=NULL;zero.p_xyz_n[2]=NULL;
Wow, here's a shortcut way to initialize your struct:
Much cleaner, yeah?Code:struct point zero = { 0 };
Also, compilers may not care about the amount/lack of whitespace, but humans usually do.
If you understand what you're doing, you're not learning anything.
are the pointers also initialized to NULL?
NULL is usually just defined as ((void *) 0) or just 0. So in short, yes they are. Use of zero or NULL to initialize pointers is stylistic, the compiler does the same initialization either way.
According to the ISO C99 standard:
Section 6.7.8, constraint #19:
Section 6.7.8, constraint: #10:The initialization shall occur in initializer list order, each initializer provided for a
particular subobject overriding any previously listed initializer for the same subobject;
all subobjects that are not initialized explicitly shall be initialized implicitly the same as
objects that have static storage duration.
In short, yes.If an object that has automatic storage duration is not initialized explicitly, its value is
indeterminate. If an object that has static storage duration is not initialized explicitly,
then:
— if it has pointer type, it is initialized to a null pointer;
— if it has arithmetic type, it is initialized to (positive or unsigned) zero;
— if it is an aggregate, every member is initialized (recursively) according to these rules;
— if it is a union, the first named member is initialized (recursively) according to these
rules.
If you understand what you're doing, you're not learning anything.
thanks for the help guys..
