extern(C++, ns) is wrong

Atila Neves atila.neves at gmail.com
Mon Sep 17 12:57:10 UTC 2018


On Sunday, 16 September 2018 at 17:46:26 UTC, Steven 
Schveighoffer wrote:
> On 9/14/18 6:41 PM, Neia Neutuladh wrote:
>
>> Specifically, Walter wants this to compile:
>> 
>> module whatever;
>> extern(C++, foo) void doStuff();
>> extern(C++, bar) void doStuff();
>> 
>> And he's not too concerned that you might have to use doubly 
>> fully qualified names to refer to C++ symbols, like:
>> 
>> import core.stdcpp.sstream;
>> import core.stdcpp.vector;
>> core.stdcpp.vector.std.vector v;
>
> This is probably the best explanation of why the current 
> situation sucks.
>
> -Steve

Agreed. Up until now, I didn't even understand the rationale for 
why it works the way it does.


More information about the Digitalmars-d mailing list