>>7
thats a pretty lame ass attempt to shoot down D:
Unicode is dealt with in a somewhat strange way - there are three different unicode string types: char[], wchar[] and dchar[] - the standard is char[]
boo hoo, sry you dont like unicode
>Arrays are strange. Some are static, some are dynamic.
as opposed to what? C++ arrays that are static pointers? having to turn arrays into objects so you can make them dynamic in C++?
Arrays are not regular objects
see above, enjoy your buffer overflows with regular non-bounds checked arrays in C++
You can sometimes call methods without the parens.
ooooh, thats a deal breaker
Functions that form closures or are attached to objects (i.e. methods) are not the same as regular functions, instead they are called delegates, and you must be aware of the differences.
seriously, this is a ~bad~ part of D compared to C++?
>Literal strings (char[]) can be defined with x"40fe", to specify the bytes in hexadecimal that make up the utf-8 array. The D website says that specifying an illegal utf-8 sequence is allowed, but my compiler disagrees.
boo hoo, compare that to how C++ handles utf-8
Im not going to go through the rest, you get the idea, its pretty pathetic to see C++ programmers try to shoot down D especially when the only way to make C++ more dynamic is on top of generics bullshit