Mercurial > projects > ldc
view tests/mini/arrays7.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 | 44f08170f4ef |
children |
line wrap: on
line source
module arrays7; extern(C) int printf(char*, ...); struct S { int i; float f; long l; void print() { printf("%d %f %lx\n", i, f, l); } } void main() { S[] arr; S s; assert(arr.length == 0); arr ~= s; assert(arr.length == 1); arr ~= S(1,2.64,0xFFFF_FFFF_FFFF); assert(arr.length == 2); arr[0].print(); arr[1].print(); assert(arr[1].i == 1); assert(arr[1].f > 2.63 && arr[1].f < 2.65); assert(arr[1].l == 0xFFFF_FFFF_FFFF); }