On Tuesday, 30 September 2014 at 14:34:49 UTC, Ola Fosheim
Grøstad wrote:
Guys I beg you, is there any chance I will get my answers? ;)
Nope :)
I suspected so :P
I don't think anyone know what extended C++ actually will look
like.
Great.
Some people say D is going to have std::* support, but that
would require someone to keep track of changes in all the c++
compilers D is supposed to support: Clang, G++, and VC++…
My thoughts too. Seems like maintenance hell.
Some people say they want full support for C++ exceptions, some
say it is too difficult…
However, you don't need std::* or C++ exceptions for a game?
Some aspects of "extended C++ support" is going to be either
wishful thinking or non-portable, so you probably should try to
avoid depending on it. What are you missing?
I use both std/boost and exceptions when makes sense - game is
not just rendering and number crunching after all.
Tbh what I -am missing- is proper run-time support for what is
already suppose to work (building x64 C++/D app crashes when
calling writeln() from D side). Win32 support is coming but I
expect similar problems (is nobody really mixing C++ and D using
VC++ atm?).
It would be great to be able to call non-virtual members of C++
classes from D but
I don't really need anything else from the language SPECS to
start things going - my question is out of pure curiosity.
That being said my biggest fear is that D2 will never be
finished... I am lurking on those forums for 2 years now, waiting
for the signal to start the transition but I need to be sure that
in few months everything I need and the code I write will work as
expected (and on iOS too). I am not seeing this unfortunately,
language is still being actively discussed on the most basic
level (allocators, ARC, auto-decoding of utf strings...). It
looks like Phobos might need to be rewritten entirely and soon. I
will not give up tho, if I must skip D for one more project
(which lasts year or two) then be it, hopefully I will be able to
use if for the nest one :(
