Specifying C++ symbols in C++ namespaces

Dicebot public at dicebot.lv
Sat Apr 5 08:24:30 PDT 2014


On Saturday, 5 April 2014 at 13:11:27 UTC, Ola Fosheim Grøstad 
wrote:
> On Saturday, 5 April 2014 at 12:58:54 UTC, Dicebot wrote:
>> It shouldn't. The fact how entity is exposed via some external 
>> binary interface should not have any notable impact on D side 
>> of things (unless you dwell into ABI realm).
>
> This is a design philosophical issue, you can make it normative 
> if you want, but only if it is consistent with the overall 
> design philosophy.

This is very practical thing. By introducing special constructs 
to support some foreign language you open the can of worms. Where 
does one stop? Should we also expect adding some new idioms for 
better JNI support? Or Python? I can't see any reason why C++ has 
to be any special and you can't nicely support them all. We don't 
even truly do this for C and this the only real ABI standard.


More information about the Digitalmars-d mailing list