view tests/mini/classinfo5.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 8d46c475842a
children
line wrap: on
line source

extern(C) int printf(char*, ...);

class BaseClass {} 
 
void main() 
{ 
    Object o_cr = BaseClass.classinfo.create();
    Object o_new = new BaseClass;
    printf("CIaddr: %X\n", cast(size_t*)BaseClass.classinfo);
    printf("Create: %X\n", cast(size_t*)o_cr.classinfo);
    printf("New:    %X\n", cast(size_t*)o_new.classinfo);
    assert(cast(size_t*)o_cr.classinfo == cast(size_t*)o_new.classinfo);
}