== Quote from Kagamin (s...@here.lot)'s article
> Iain Buclaw Wrote:
> > Anyway, yes I believe this would be the expected behaviour. GDC has a
> > slightly
> > different strategy than DMD to ensure symbols that are supposed to be only
> > linked
> > once are done so correctly.
> Haha, just by mak
Iain Buclaw Wrote:
> Anyway, yes I believe this would be the expected behaviour. GDC has a slightly
> different strategy than DMD to ensure symbols that are supposed to be only
> linked
> once are done so correctly.
Haha, just by making sure they're always linked? :)
What is this strategy? I me
== Quote from Kagamin (s...@here.lot)'s article
> ---
> struct BL{int OAT=42;}
> BL[1024][64][4] bloat;
> void foo()
> {
> bloat[0][0][0].OAT=1;
> }
> void goo(){}
> ---
> I compile this file and archive it to a library and then link to another file.
> If goo is used, bloat also gets into exe
---
struct BL{int OAT=42;}
BL[1024][64][4] bloat;
void foo()
{
bloat[0][0][0].OAT=1;
}
void goo(){}
---
I compile this file and archive it to a library and then link to another file.
If goo is used, bloat also gets into executable, which is not true for dmd.
Is this expected behavior or
