> Could we also get "=numbered" and "=term" directives that are
> equivalent to "=item :numbered" and "=item :term", respectively, for
> use with abbreviated blocks? E.g.:
>
> =numbered First Item
> =numbered Second Item
> =numbered Third Item
That's just:
=item # First Item
=item # Second Item
=item # Third Item
or even just:
=item# First Item
=item# Second Item
=item# Third Item
> =term First Name
> Definition
> =term Second Name
> Definition
This doesn't work, because it doesn't conform to the general syntax
of abbreviated blocks (which is that the content starts immediately
after the typename). The term of a term/definition is basically a
very complicated bullet point, and hence needs to be configured with
an option.
Of course, we could make a special exemption to the general syntax, or
say that in this one case the first line of content is special, but I'm
*really* loathe to inject special cases when a general mechanism
already exists.
> Within tables, you should probably replace "whitespace" with "multiple
> whitespace" as a column delimiter; otherwise, the space between two
> words in an identifier would trigger a new column:
Indeed. That was both the intention and the implementation in Perl6::Perldoc,
but it definitely needs to be mentioned explicitly. Thank-you.
> When using the code block alias, are the outermost curly braces
> considered to be part of the ambient code?
Yes. All ambient code is actual code.
> Why is =END a block, and not a directive?
Damn good question. I can't think of any reason off the top of my head.
I'll need to ponder that.
Damian
