On 2 March 2012 23:16, Bernard Helyer <span dir="ltr">&lt;<a href="mailto:b.helyer@gmail.com">b.helyer@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Friday, 2 March 2012 at 11:53:56 UTC, Manu wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Personally, I just want to be able to link like a normal windows developer.<br>
My code is C/C++, built with VC, and I want to link my D app against those<br>
libs using the VC linker, and debug with Visual Studio. This is the<br>
workflow I think the vast majority of Windows devs will expect, and it<br>
sounds simple enough. This is the only thing standing between me using D<br>
for any major projects, and just experimenting with the language for<br>
evaluation, or just academic interest.<br>
64bit is far less important to me personally, VisualC linker compatibility<br>
is the big one. I just want to link against my C code without jumping<br>
through lots of hoops.<br>
</blockquote>
<br></div>
No one thinks that&#39;s a bad idea. The trouble is the amount of developers that actually understand the backend enough to implement another object format (which is what&#39;s needed to support the VisualC linker) is very small.<br>

<br>
What&#39;s needed is someone to take the time to learn it then do it. Someone motivated, and smart. Not unlike yourself! :P<br>
</blockquote></div><br><div>Haha, ohhh, I see what you did there.</div><div>Well played...</div>