This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
I guess this means that we now have mixed C++98 and C++11 support in the mangler, and no way to choose (on the D side) whether we explicitly want one or the other?
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I originally went full C++11 but throwle failed to link.
Do you have any document about the mangling changes between 98 and 11 ?
I didn't find anything relevant and figured this was too big of a matter to address in this PR.
importcore.stdc.stdio;
// Disabled on windows because it needs bindings
// Disabled on osx32 because size_t is not properly mangled
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters