initializer needs constant

[Mantorok Redgormor]

struct mystruct {
int a;
int b;
};

struct mystruct x = { 10, 10 }, y = x;

What section in the standard says that y needs a constant?
And why can't it resolve x so that y can have a copy of its values?

--
nethlek

[Mark A. Odell]

ne*****@tokyo.com (Mantorok Redgormor) wrote in
news:41*************************@posting.google.co m:

struct mystruct {
int a;
int b;
};

struct mystruct x = { 10, 10 }, y = x;

What section in the standard says that y needs a constant?
And why can't it resolve x so that y can have a copy of its values?

const int foo = 10;
int bar = foo; <-- error: initializer element is not constant

const int foo = 10;

does not mean foo is a constant, it means the compiler will not allow you
to assign a value to foo other than an initializer. You need a real
constant, not a const variable.

--
- Mark ->
--

[A. Bolmarcich]

In article <41*************************@posting.google.com> , Mantorok Redgormor wrote:

struct mystruct {
int a;
int b;
};

struct mystruct x = { 10, 10 }, y = x;

What section in the standard says that y needs a constant?
And why can't it resolve x so that y can have a copy of its values?

In ISO/IEC 9899:1990 the "Constraints" subsection of the
"6.5.7 Initialization" section contains the sentence:

All the expressions in an initializer for an object that has
static storage duration or in an initializer list for an object
that has aggregate or union type shall be constant
expression.