I understand, that this was the way D was designed initially. But the directly unrelated modules are both involved in the process willfully by using some mixins. They know what they&#39;re doing. They&#39;re not _completely_ unrelated.<div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Nov 27, 2012 at 10:58 PM, David Nadlinger <span dir="ltr">&lt;<a href="mailto:see@klickverbot.at" target="_blank">see@klickverbot.at</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tuesday, 27 November 2012 at 18:57:09 UTC, Gor Gyolchanyan wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
different directly unrelated modules could<br></div>
contribute to the code generation process […]<br>
</blockquote>
<br>
And one of the main design goals of the D module system is precisely that »different directly unrelated modules« don&#39;t affect each other. ;)<span class="HOEnZb"><font color="#888888"><br>
<br>
David<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Bye,<br>Gor Gyolchanyan.<br>
</div>