August 29, 2014 [Issue 13396] New: Non-instance and final methods on extern(C++) interfaces shouldn't be mangled as C++ names | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=13396 Issue ID: 13396 Summary: Non-instance and final methods on extern(C++) interfaces shouldn't be mangled as C++ names Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: regression Priority: P1 Component: DMD Assignee: nobody@puremagic.com Reporter: blah38621@gmail.com A while back, some changes were made to the C++ mangling, those changes broke the build on an old project of mine which declared the following: extern(C++) public interface ScriptObject // Total size: 0x3C { public: final static T Find(T)(string name) { return T.init; } } and, in another file, it does: ScriptObject.Find!SomeObjectType("SomeObjectType"); This instantiates the template, and the current DMD tries to mangle Find as a C++ function, which obviously fails, because string isn't something you can mangle for C++. I believe that methods with implementations in extern(C++) interfaces should still be using the D calling convention and mangling scheme. -- |
Copyright © 1999-2021 by the D Language Foundation