C++ interop - what to do about long and unsigned long?

Manu via Digitalmars-d digitalmars-d at puremagic.com
Fri Sep 12 18:36:23 PDT 2014


On 12 September 2014 17:44, Daniel Murphy via Digitalmars-d <
digitalmars-d at puremagic.com> wrote:

> "Manu via Digitalmars-d" <digitalmars-d at puremagic.com> wrote in message
> news:mailman.789.1410494842.5783.digitalmars-d at puremagic.com...
>
>  So, can we talk about virtual by default again?
>> Daniel Murphy was behind it wrt c++ compatibility.
>> It's still driving me insane. All things I said will happen do happen,
>> constantly.
>>
>
> It's not required for C++ interop, it's just a huge pain in the ass since
> you have to mark nearly every function as final.
>

Yeah, but that's true regardless of C++ interop. It's so easy to make
mistakes, and so hard to find them when you do. virtual-by-default is
responsible for most of the silent errors in my code by far.
Surely, at very least, an extern(C++) class should be final-by-default?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20140913/55da3977/attachment.html>


More information about the Digitalmars-d mailing list