view tests/mini/classinfo3.d @ 1499:df11cdec45a2

Another shot at fixing the issues with (constant) struct literals and their addresses. See DMD2682, #218, #324. The idea is to separate the notion of const from 'this variable can always be replaced with its initializer' in the frontend. To do that, I introduced Declaration::isSameAsInitializer, which is overridden in VarDeclaration to return false for constants that have a struct literal initializer. So {{{ const S s = S(5); void foo() { auto ps = &s; } // is no longer replaced by void foo() { auto ps = &(S(5)); } }}} To make taking the address of a struct constant with a struct-initializer outside of function scope possible, I made sure that AddrExp::optimize doesn't try to run the argument's optimization with WANTinterpret - that'd again replace the constant with a struct literal temporary.
author Christian Kamm <kamm incasoftware de>
date Sun, 14 Jun 2009 19:49:58 +0200
parents 8f0b24bc55f0
children
line wrap: on
line source

module classinfo3;

class C
{
    int i;
    float f;
    long l;
    int j;
}

void main()
{
    auto c = C.classinfo;
    if (c.offTi !is null)
    {
    assert(c.offTi.length == 4);

    size_t base = 2*size_t.sizeof;

    assert(c.offTi[0].offset == base);
    assert(c.offTi[0].ti == typeid(int));
    assert(c.offTi[1].offset == base+4);
    assert(c.offTi[1].ti == typeid(float));
    assert(c.offTi[2].offset == base+8);
    assert(c.offTi[2].ti == typeid(long));
    assert(c.offTi[3].offset == base+16);
    assert(c.offTi[3].ti == typeid(int));
    }
}