Bill Baxter wrote: > So more like > const int y=3+x; > const int x=5+y; > > No matter which order you scan that, you can't come to a valid order of > initialization. I get that, really, I do. I just wanted to point out why 'Surely that's just an "x is not defined on line 2" error?' does not hold, nor is to the point (which you just repeated). Regards, frank