C structure initialization with variable

Question

I've run into a problem that seems to not be addressed by any of the C Standards after C89 save for the mention that structures initialization limits had been lifted. However, I've run into an error using the Open Watcom IDE (for debugging) where the compiler states that the initializer must be a constant expression.

Here's the gist of what's going on.

typedef struct{
 short x;
 short y;

} POINT;

void foo( short x, short y )
{
 POINT here = { x, y }; /* <-- This is generating the error for the compiler */

 /* ... */

}

Any ideas why, or what standard disallows that?

I don't know the answer to your question but I would recommend you create a function like: POINT createPOINT(x,y) to init all your POINT type vars. — El Developer
– El Developer, Commented Oct 9, 2011 at 1:38

Omri Barel · Accepted Answer · 2011-10-09 01:43:40Z

6

The following quote is from the C99 rationale:

The C89 Committee considered proposals for permitting automatic aggregate initializers to consist of a brace-enclosed series of arbitrary execution-time expressions, instead of just those usable for a translation-time static initializer. Rather than determine a set of rules which would avoid pathological cases and yet not seem too arbitrary, the C89 Committee elected to permit only static initializers. This was reconsidered and execution-time expressions are valid in C99.

answered Oct 9, 2011 at 1:43

Omri Barel

9,5483 gold badges31 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Caleb Waggoner Over a year ago

AH! So that's another C99 feature. That explains why only Watcom's compiler had problems with it. Thanks.

Mark Robinson · Accepted Answer · 2011-10-09 01:37:56Z

2

The problem is that C isn't an Object language and only does strict typing. Further, C maintains a difference between structs and arrays.

The way your code will have to work is

void foo( short x, short y )
{
 POINT here; 
 here.x = x;
 here.y = y;
}

answered Oct 9, 2011 at 1:37

Mark Robinson

3,1951 gold badge26 silver badges40 bronze badges

3 Comments

Caleb Waggoner Over a year ago

I know that's a fix for it, I was more wondering why Watcom's compiler throws the error when others (gcc and MSVC to be specific) do not... Do you suppose that Watcom still operate on pre-C89 standards?

Mark Robinson Over a year ago

That's entirely possible. Not all compilers meet the spec entirely.

Andrew Marshall Over a year ago

GCC by default does not strictly compile against C89 unless you specify -ansi or std=c89. By default it is C89 with certain C99 features. Arguably you should always compile against a standard with GCC for portability.

Dmitri · Accepted Answer · 2011-10-09 01:46:41Z

0

This is normal for C89... initializers do need to be constant, ie. able to be determined at compile time. This means no variables in initializers, and it's true for other types as well, not just structs. In C99, your code would work.

answered Oct 9, 2011 at 1:46

Dmitri

9,4052 gold badges30 silver badges36 bronze badges

Collectives™ on Stack Overflow

C structure initialization with variable

3 Answers 3

1 Comment

3 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related