On 9/10/21 4:48 AM, Ron Tarrant wrote:
> On Friday, 10 September 2021 at 10:59:10 UTC, bauss wrote:
>
>> Publisher : CreateSpace Independent Publishing Platform; 1st
>> edition (Aug. 19 2015)
>
> Yeah, I saw that, too. And if you do a "Look inside," the copyright date
> is 2019... thus my question. :)
tldr; Yes, it's print-on-demand and 2019 is correct for the current
print edition. I would download the PDF version from ddili.org.
The following is a list of different versions of the book.
1) The git clone on my computer is the newest, which I may sit on for
weeks for minor corrections. (These corrections are recommended by most
of you; thank you!) So, this version would have today's date and the
code samples in the book (some of them) would be checked with the dmd
version installed on my computer.
2) Although updating the site is pretty much automated and free, I may
not bother updating the site for minor corrections.
If you are happy with a PDF version, the PDF at ddili.org is almost
always newer and formatted in almost exactly the same way. The only
format differences are that the online PDF version has colored code
samples and it does not have a book cover.
Currently, the online PDF version says
D version: 2.094.2
Book revision: 2021-02-26
3a) The PDF version given to the printers is older partly because
updates have some restrictions (e.g. a number of times per certain
number of weeks) and updating them requires some labor.
I see from your message that the current print versions are from 2019.
3b) The ebook versions may be even older mostly because they require
much more labor. (Passing the HTML through Calibre , clicking the
correct boxes, etc.)
But I think the ebook versions are the same as the printer versions as
of this writing.
Although I am very happy with the appreciation it gets, of course there
are many parts of the book that I want to improve. Some parts even make
me cringe. :)
- I am embarrassed that the copy constructors still are not in the book.
(Post-blit is featured.)
- I want to rewrite parts of the "Imutability" chapter after emails from
Don Allen. It was written before I understood immutable better. There
are many examples in the book that use 'immutable' even though I always
use 'const' in my own code:
immutable a = Foo(); // Should be only when really necessary
const b = Foo(); // Should be used almost always
I see people write 'immutable' on these forums and I feel guilty about
it. :/
- I can't understand where I got the initial motivation to finish the
book. I don't have it now. :/
- I want to thank Steven Schveighoffer here once more for his help with
the book. I later realized that his name should have much more
prominence. I can't understand how my older self did not realize this
fact when the book was being finalized.
Ali
