initializer element

[Mark]

gcc-4.2.3 isn't happy with the following snippet:

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...
}

int main(void)
{
foo("xyz");
return 0;
}

What am I doing wrong?

 

[Ian Collins]

gcc-4.2.3 isn't happy with the following snippet:

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...
}

int main(void)
{
foo("xyz");
return 0;
}

What am I doing wrong?

Not using C99 mode?

 

[Vincenzo Mercuri]

Mark ha scritto:

gcc-4.2.3 isn't happy with the following snippet:

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...
}

int main(void)
{
foo("xyz");
return 0;
}

What am I doing wrong?

Also #include <stdio.h> at least, so NULL won't stay undeclared

 

[Mark]

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...

[skip]

Not using C99 mode?

Yes, indeed. Such kind of initialization of array elements appeared in C99 ?

 

[Vincenzo Mercuri]

Mark ha scritto:

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...

[skip]

Not using C99 mode?

Yes, indeed. Such kind of initialization of array elements appeared in
C99 ?

Yes, only C99 allows you to initialize an array element
with a nonconstant expression (in this case: the pointer p).

 

[Keith Thompson]

Mark ha scritto:

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...

[skip]

Not using C99 mode?

Yes, indeed. Such kind of initialization of array elements appeared in
C99 ?

Yes, only C99 allows you to initialize an array element
with a nonconstant expression (in this case: the pointer p).

And only if the object being initialized has automatic storage duration
(which it does in this case).

 

[Keith Thompson]

Mark ha scritto:

gcc-4.2.3 isn't happy with the following snippet:

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...
}

int main(void)
{
foo("xyz");
return 0;
}

What am I doing wrong?

Also #include <stdio.h> at least, so NULL won't stay undeclared

Or #include <stddef.h> if you're not doing any I/O. NULL is defined in
several different standard headers.

 

[Vincenzo Mercuri]

Keith Thompson ha scritto:

Mark ha scritto:

gcc-4.2.3 isn't happy with the following snippet:

void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...
}

int main(void)
{
foo("xyz");
return 0;
}

What am I doing wrong?

Also #include<stdio.h> at least, so NULL won't stay undeclared

Or #include<stddef.h> if you're not doing any I/O. NULL is defined in
several different standard headers.

Yes, with 'at least' I meant that 'stdio.h' would be one
of the ways to have NULL declared. But actually 'stddef.h'
would be more suitable to that example.

 

[Vincenzo Mercuri]

Keith Thompson ha scritto:

Mark ha scritto:

Ian Collins wrote:
void foo(char *p)
{
/* warning: initializer element is not computable at load time. */
char *my_argv[] = { "abc", p, "def", NULL };
...


[skip]

Not using C99 mode?
Yes, indeed. Such kind of initialization of array elements appeared in
C99 ?

Yes, only C99 allows you to initialize an array element
with a nonconstant expression (in this case: the pointer p).

And only if the object being initialized has automatic storage duration
(which it does in this case).

Exactly!