On Sat, Jan 5, 2013 at 10:09 PM, Walter Bright <newshound2@digitalmars.com> wrote:
On 1/5/2013 7:14 AM, Philippe Sigaud wrote:Having macros in Ddoc have been a godsend for improving productivity. For example, some bits need to be added or removed for generating an ebook - macros handle that in an ideal fashion. They're great for adding boilerplate, when urls need to be mass changed, etc. It just goes on.
Since I just remade a 180-pages tutorial on D templates in markdown without much
trouble, I guess documentation and tutorial are different beasts. I felt no need
for macros, really, but I can see how they are useful for Ddoc pages.
You know, I always felt Ddoc was a strange sublanguage bolted onto D. An elegant
solution would be to have macros be D code, but I have nothing to propose here.
It is a strange sublanguage. It has its problems, but compared to what D documentation was like before Ddoc, it is a HUGE and incalculable leap forward.
The Phobos documentation, for example, before Ddoc was complete and utter garbage that rarely had any correspondence to what the code actually was and did.
And, btw, I have published on Amazon a couple of non-tech ebooks. I used Ddoc for them, and there is no html feel to the result. They look like any other ebook.