We should write a book about D, or even a D for C++ programmers book. It
would probably only be a handfull of chapters, and one or a couple
people could do each chapter. maybe even do it on a wiki or something. I
dont know how the styles would mesh but I just thought this would be
pretty cool to have.

We should write a book about D, or even a D for C++ programmers book. It
would probably only be a handfull of chapters, and one or a couple
people could do each chapter. maybe even do it on a wiki or something. I
dont know how the styles would mesh but I just thought this would be
pretty cool to have.

We should write a book about D, or even a D for C++ programmers book. It
would probably only be a handfull of chapters, and one or a couple
people could do each chapter. maybe even do it on a wiki or something. I
dont know how the styles would mesh but I just thought this would be
pretty cool to have.

We should write a book about D, or even a D for C++ programmers book. It
would probably only be a handfull of chapters, and one or a couple
people could do each chapter. maybe even do it on a wiki or something. I
dont know how the styles would mesh but I just thought this would be
pretty cool to have.

That book is not arranged like a book. Nobody could actually learn D
from it, even if it was fleshed out. It needs to be scrapped.

Sorry for my far-too-obtuse reference. ;-)
What I was trying to get across was that there already exists a wiki
platform for writing online books. As an example, there is the beginnings
of a D Reference manual. If one wanted to, one could also use the same
platform to write a "How To Program using D" style of book.
As a start, why not write your proposed TOC as the opening page in such a
new endeavor. I know I would like to contribute to it.
--
Derek Parnell
Melbourne, Australia
"Down with mediocrity!"

We should write a book about D, or even a D for C++ programmers book. It
would probably only be a handfull of chapters, and one or a couple
people could do each chapter. maybe even do it on a wiki or something. I
dont know how the styles would mesh but I just thought this would be
pretty cool to have.

from it, even if it was fleshed out. It needs to be scrapped.

Sorry for my far-too-obtuse reference. ;-)
What I was trying to get across was that there already exists a wiki
platform for writing online books. As an example, there is the beginnings
of a D Reference manual. If one wanted to, one could also use the same
platform to write a "How To Program using D" style of book.
As a start, why not write your proposed TOC as the opening page in such a
new endeavor. I know I would like to contribute to it.

The main problem I have with wikibook is that, without somebody as the
official, ordained editor, often people feel that they shouldn't make
large rearrangements, when often it's the best solution. So, it can
become fairly stagnant after the original editor either becomes
disinterested or simply "finishes" it in his mind.
- Gregor Richards
PS: I'll start one this evening.

Great, what target audience do you have in mind? From the looks of the
TOC it seems beginner. Maybe that is a suggestion, to keep in mind? Then
perhaps the book should also adress or refer to programming and
computer topics more general. Another option is to split it in parts or
some other way of organization according to background of readers.
Lack of books and tutorials is one of the arguments people have to not
try D. It's partly true I guess, especially for beginners / novices.
Even with one reasonable good wikibook I think D will beat C++ as a
first language - and a lot of people start with C++.
Gregor Richards wrote:

Derek Parnell wrote:

On Tue, 05 Sep 2006 15:17:05 -0700, Gregor Richards wrote:

Derek Parnell wrote:

On Mon, 04 Sep 2006 02:31:12 -0400, Agent Orange wrote:

We should write a book about D, or even a D for C++ programmers
book. It would probably only be a handfull of chapters, and one or
a couple people could do each chapter. maybe even do it on a wiki
or something. I dont know how the styles would mesh but I just
thought this would be pretty cool to have.

from it, even if it was fleshed out. It needs to be scrapped.

Sorry for my far-too-obtuse reference. ;-)
What I was trying to get across was that there already exists a wiki
platform for writing online books. As an example, there is the beginnings
of a D Reference manual. If one wanted to, one could also use the same
platform to write a "How To Program using D" style of book.
As a start, why not write your proposed TOC as the opening page in such a
new endeavor. I know I would like to contribute to it.

The main problem I have with wikibook is that, without somebody as the
official, ordained editor, often people feel that they shouldn't make
large rearrangements, when often it's the best solution. So, it can
become fairly stagnant after the original editor either becomes
disinterested or simply "finishes" it in his mind.
- Gregor Richards
PS: I'll start one this evening.

We should write a book about D, or even a D for C++ programmers
book. It would probably only be a handfull of chapters, and one or
a couple people could do each chapter. maybe even do it on a wiki
or something. I dont know how the styles would mesh but I just
thought this would be pretty cool to have.

Sorry for my far-too-obtuse reference. ;-)
What I was trying to get across was that there already exists a wiki
platform for writing online books. As an example, there is the
beginnings
of a D Reference manual. If one wanted to, one could also use the same
platform to write a "How To Program using D" style of book.
As a start, why not write your proposed TOC as the opening page in
such a
new endeavor. I know I would like to contribute to it.

The main problem I have with wikibook is that, without somebody as the
official, ordained editor, often people feel that they shouldn't make
large rearrangements, when often it's the best solution. So, it can
become fairly stagnant after the original editor either becomes
disinterested or simply "finishes" it in his mind.
- Gregor Richards
PS: I'll start one this evening.

Great, what target audience do you have in mind? From the looks of the
TOC it seems beginner. Maybe that is a suggestion, to keep in mind? Then
perhaps the book should also adress or refer to programming and
computer topics more general. Another option is to split it in parts or
some other way of organization according to background of readers.
Lack of books and tutorials is one of the arguments people have to not
try D. It's partly true I guess, especially for beginners / novices.
Even with one reasonable good wikibook I think D will beat C++ as a
first language - and a lot of people start with C++.

Which is sort of terrifying, since C++ is one of those languages that
hands you a rope and noose-tying instructions.
- Gregor Richards

Lack of books and tutorials is one of the arguments people have to not
try D. It's partly true I guess, especially for beginners / novices.
Even with one reasonable good wikibook I think D will beat C++ as a
first language - and a lot of people start with C++.

C++ as a first language, ouch. I actually tried this. The examples in
the book I was using didn't work. I was too much of a newbie to
understand why. C++ wasn't very intuitive. The whole thing failed
miserably. I've heard of other people learning C++ as a first, but I
still find it hard to imagine normal human beings doing this without
being taught in a class or some sort of interactive environment.
Eventually I just learned programming through the scripting language in
the EasyUO program. It was useful, easy, and taught me some basic
programming.
I think D would make a pretty good starting language. I looked at that
TOC, maybe mention build at some point when doing modules (chap 7)? I'd
hate to have to invoke dmd on every .d file or (cringe) use makefiles.

i agree with Chad J.
i'm a beginner too, i really need a book for beginners, as long as i
don't understand a lot of programming techniques, their usefulness, etc.
it should have examples for every aspect, everything explained from the
beginning. it is hard to learn from the community as long as most of
them are hardcore programmers, they cannot assume one doesn't know what
"virtual" means or what's so great deal about "templates".
i consider the examples most important (covering all the
possibilities), theory to explain them, too, also pluses and minuses of
techniques, their importance, how much they are used, etc. mabye it
would be a good idea to have a successful c++ or java book as model,
adding specific D features when they exist.

We should write a book about D, or even a D for C++ programmers book. It
would probably only be a handfull of chapters, and one or a couple
people could do each chapter. maybe even do it on a wiki or something. I
dont know how the styles would mesh but I just thought this would be
pretty cool to have.