view tests/mini/sextzext.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 cc40db549aea
children
line wrap: on
line source

module mini.sextzext;

void main()
{
    byte sb  = sextreturn1();
    short ss = sextreturn2();
    assert(ss == -2);
    assert(sb == -2);
    assert(sextparam1(-42) == -42);
    assert(sextparam2(-42) == -42);

    ubyte ub  = zextreturn1();
    ushort us = zextreturn2();
    assert(ub == 2);
    assert(us == 2);
    assert(zextparam1(42) == 42);
    assert(zextparam2(42) == 42);

    assert(getchar() == 'a');
    assert(passchar('z') == 'z');

}

byte sextreturn1()
{
    return -2;
}
short sextreturn2()
{
    return -2;
}

ubyte zextreturn1()
{
    return 2;
}
ushort zextreturn2()
{
    return 2;
}

byte sextparam1(byte b)
{
    return b;
}
short sextparam2(short s)
{
    return s;
}

ubyte zextparam1(ubyte b)
{
    return b;
}
ushort zextparam2(ushort s)
{
    return s;
}

char getchar()
{
    return 'a';
}

char passchar(char ch)
{
    return ch;
}