Learning With D

[Jesse Phillips]

Ali Çehreli Wrote:

> On 05/21/2011 11:12 PM, Jesse Phillips wrote:
>  > This book is intended to teach programming from the ground
>  > up.
> 
> I have some experience in doing the same. Just like teaching in the 
> classroom, no matter what style or detail has been chosen, readers will 
> find the material anywhere from very easy to exteremly difficult. :)

I definitely don't expect to satisfy everyone and what I have leans on the easy, fast style.

I've some experience tutoring, and generally get compliments, but I don't know how well this translates to writing. But it is better than nothing.

>  > We all know D would make a very good first language
> 
> Agreed. Although there are so many high level concepts in the language, 
> starting to write simple programs is very easy. For example, one can go 
> a long way without even knowing that pointers exist. Additionally, 
> having to introduce the concept of a reference type earlier makes it 
> easy to explain pointers later on.

I don't think there is a right answer to this. I think classes can be harder to explain and understand then basic pointers and structures.

One aspect which I'm trying to keep in this book is, leave nothing unexplained. If I use it I don't want to just say "this is required, but don't worry about why just yet." I did this with the main function, but I'm making an effort not to make this common.

Classes have lots of things that can just be glossed over, which is fine, but it makes it very hard to explain why they do what they do.
 
>  > And I really want the user to go from first time "Python"
>  > programmer to basic "C" programmer.
> 
> I think, that is a more accurate description than the one in Chapter 1: 
> "(expected starting experience of none)". I can imagine that some people 
> will find your book a little too fast. (And others will find it too 
> slow! :))

I didn't want to mention any languages, but I suppose someone looking to learn a language will have heard of a few and have an idea of what that statement would mean.

>  > One approach that I think many will like is the Common Errors
>  > sections which is meant to help people identify what the
>  > compiler is saying when things go wrong.
> 
> That is going to be very helpful.

Yes and at some point I'll look at pulling these out and having them all in a single section and probably placed on Wiki4D.

> Thank you,
> Ali

Thank you