Mercurial > projects > ldc
annotate tests/mini/arrays13.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 | 1bb99290e03a |
children |
rev | line source |
---|---|
100 | 1 module arrays13; |
2 | |
175
c44e6a711885
[svn r191] Fixed: array literals did not support all type/storage combinations.
lindquist
parents:
100
diff
changeset
|
3 extern(C) int printf(char*, ...); |
c44e6a711885
[svn r191] Fixed: array literals did not support all type/storage combinations.
lindquist
parents:
100
diff
changeset
|
4 |
100 | 5 void main() |
6 { | |
175
c44e6a711885
[svn r191] Fixed: array literals did not support all type/storage combinations.
lindquist
parents:
100
diff
changeset
|
7 char[] a = "hello"; |
100 | 8 |
9 assert(a > "hel"); | |
10 assert(a >= "hel"); | |
11 assert(a < "helloo"); | |
12 assert(a <= "helloo"); | |
13 assert(a > "betty"); | |
14 assert(a >= "betty"); | |
15 assert(a == "hello"); | |
16 assert(a <= "hello"); | |
17 assert(a >= "hello"); | |
18 } |