Still better, then a completely separate thing.<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 28, 2012 at 9:09 PM, jerro <span dir="ltr">&lt;<a href="mailto:a@a.com" target="_blank">a@a.com</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 Wednesday, 28 November 2012 at 17:02:25 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">
Precisely!<br>
<br>
<br>
On Wed, Nov 28, 2012 at 8:59 PM, jerro &lt;<a href="mailto:a@a.com" target="_blank">a@a.com</a>&gt; wrote:<br>
<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wednesday, 28 November 2012 at 15:51:50 UTC, Gor Gyolchanyan wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think that would be a huge mistake. Why would anyone want to invent a<br>
full blown language and a big pain in the butt just to build a project if<br>
the project can build itself by looking at the source code?<br>
<br>
</blockquote>
<br>
The build system could be a library written in D, then you wouldn&#39;t need<br>
to invent a new language.<br>
</blockquote></div></div></blockquote>
<br>
I mean&#39;t writing a D build library and using it to write build scripts separate from the source files that are being build. That&#39;s quite different from embedding build instructions into comments inside the source files.<br>

</blockquote></div><br><br clear="all"><div><br></div>-- <br>Bye,<br>Gor Gyolchanyan.<br>
</div>