A little Py Vs C++

[H. S. Teoh]

On Thu, Nov 01, 2012 at 08:49:40PM +0100, Rob T wrote:
> On Thursday, 1 November 2012 at 18:06:21 UTC, Peter Alexander wrote:
> >
> >The same is true in D. Well-written D code often does look rather
> >elegant, but the amount of understanding needed to write beautiful
> >D code is staggering.
> 
> I'll second that!
> 
> I'm finally making good progress with D after a whole lot of effort,
> and there were (and still are) periods where I felt like giving up,
> although not so much anymore.
> 
> The number one missing item that I would love to get my hands on is
> comprehensive documentaion. What we have now leaves out far too much
> detail, and may be missing entire features, and what is available is
> scattered all over the place.
> 
> Reading the TDPL book is a huge help for understanding D, it's
> essential reading for sure, but it's only an overview rather than a
> full text on the subject. The TDPL lacks many of the fine details
> that one needs to know in order to write proper D code. I find
> myself experimenting a lot in order to figure out what the various
> obscure details are, but without comprehensive documentation, I
> cannot be certain if the observed behaviours are actually correct or
> fully complete under all situations.

Ali's D book might be helpful: http://ddili.org/ders/d.en/index.html

But yeah, the current documentation needs work. Unfortunately, wishing
for it to happen won't make it happen, so if you contribute (use the
"improve this page" link) that would be great, and suggestions are also
helpful. I recently revised the docs for std.range to explain briefly
what ranges are and why we even need them, but this is only one piece of
the entire standard library. Many other modules need improved docs. And
there is still the need for a general overview to put everything in
perspective.


T

-- 
It is impossible to make anything foolproof because fools are so ingenious. -- Sammy