Re: What the?

The lack of initializers is a real problem. For example, suppose I go through a lot of
effort to create a new class where I re-implement 'new' and 'delete' to work on my own
allocator structures. I want to do

#pragma data_seg("shared")
DWORD base;
MyTypeCollection data[SOME_LIMIT_HERE] = ?;
#pragma data_seg()

Note that for a type to be in the specified data segment, I must have an initializer, but
I *can't* have an initializer. So the use of C++ object collections in shared segments is
precluded unless I do something really complex with placement constructors, and that has
its own set of problems.

As I said in an earlier post, I use the C-style arrays when I need
compile-time-constant-initialized values, because there is no initialization construct in
C++ (and it is not clear why this is so; I see no reason I couldn't write

static const Complex points[] = {
        Complex(1, 0),
        Complex(1, 1),
        Complex(pi, 0),
        Complex(pi, 1),
        ...etc.
        };

except some issue that it was thought this was "not a good idea".
                joe