<p><br>
On May 5, 2013 5:20 PM, "&<a href="mailto:lt%3Bluismarques@gmail.com">lt;luismarques@gmail.com</a>&<a href="mailto:gt%3B%26quot%3B@puremagic.com">gt;"@puremagic.com</a>" <"\"Luís".Marques"> wrote:<br>
><br>
> On Sunday, 5 May 2013 at 13:33:25 UTC, Iain Buclaw wrote:<br>
>><br>
>> 1. Support extern(C++) classes so can have a split C++/D implementation of eg: Expression and others.<br>
><br>
><br>
> I don't know if this will be in the videos, so I'll ask here. I thought extern(C++) only supported interfaces because everything else fell into the "we'd need to pretty much include a C++ compiler into D to support that" camp. Is that not quite true for classes? Did you find some compromise between usefulness and complexity that wasn't obvious before, or did the D compiler transition just motivate adding some additional complexity that previously wasn't deemed acceptable?</p>
<p>It was mentioned, however I do believe there are a few more complicated things than that. Many would be in a position to educate you on that. </p>
<p>Regards<br>
-- <br>
Iain Buclaw</p>
<p>*(p < e ? p++ : p) = (c & 0x0f) + '0';<br>
</p>