On 1/1/2015 5:47 PM, Mike Parker wrote:
On 1/2/2015 7:10 AM, Walter Bright wrote: Besides, consider how many tasks the macros in Phobos handle that are common enough for most projects to need them. Shouldn't that sort of thing be built in? Why should we keep putting together LIST macros when a list is a very common documentation feature? It's nice to be able to redefine that macro for different types of markup output, but I would much rather see a standard list tag that simply outputs HTML. I can use one of several tools to convert the HTML to something else if I need to.
Because all those features come up with the cost, such as adding a way to work around them.
BTW, you can embed HTML directly. No need to use the macros.
