Specifying C++ symbols in C++ namespaces
Ola Fosheim Grøstad" <ola.fosheim.grostad+dlang at gmail.com>
Ola Fosheim Grøstad" <ola.fosheim.grostad+dlang at gmail.com>
Sat Apr 5 06:11:26 PDT 2014
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.
Working on making that philosophy explicit is important, D2 is
showing some signs of having gone through a lot of evolutionary
design and IMHO signs of a need for notational redesign. Meaning:
recreate the syntax to fit the desired semantics that the
language has obtained over time (as in designing it, not
evolving).
Not distinguishing between C++/D does however have consequences:
if foreign constructs have the same appearance as the language
constructs then you should also make sure that all the semantics
are the same. E.g. C++ exceptions, calls to C++ new etc have to
be fully harmonized with D equivalents.
More information about the Digitalmars-d
mailing list