Executable size affected by module count?

[kris]

Walter Bright wrote:
> kris wrote:
> 
>> There's no real surprise that this would happen, but it's the actual 
>> difference that is cause for a little concern -- it appears that each 
>> module consumes 512 bytes minimum. This may actually be a linker 
>> thing, but perhaps not?
> 
> 
> The way to see what's in an object file is to run obj2asm on it. It'll 
> show exactly what's submitted to the linker.
> 

I'm aware of that, thanks.

Do you think you could comment on why it might be the linker? And how to 
compensate? You're probably one of the two ppl in the world who know 
OptLink ...

Also: are dmd obj files compatible with any other linker?