Of course, I forgot about deallocaion, so allocators would be defined as something like:

// somewhere...

I like the above suggestions. After thinking about it, I'm beginning to wonder if...

Yes.

It used to be the only way that worked. Early C compilers couldn't cope...

Confusing.. I thought const in D meant really 'constant'. If a const in a function...

int foo(int x)
{
    static const i = x;	// error, x is not const
    const j...

a static in a class is well defined. so is a const. for me 'static...

In a function?
In a class?

--bb

Does it really make sense to have the programmer decide this distinction? A global const...

Hrm... so the compiler would have to do something like generate a dummy variable referencing...