Re: expanding =begin

Ricardo Signes wrote:
> 
> I'd like to extend this definition a bit.  I would replace the second paragraph
> with:
> 
>    "=begin formatname"
>    "=begin formatname parameter"
...
>        It is advised that formatnames match the regexp
>        "m/\A:?[−a−zA−Z0−9_]+\z/".  Everything following whitespace after the
>        formatname is a parameter that may be used by the formatter when dealing
>        with this region.  Implementors should anticipate future
>        expansion in the semantics and syntax of the first parameter to
>        "=begin"/"=end"/"=for".

+1

> This allows for constructions like:
> 
>   =begin syntax javascript
> 
>   =end syntax
> 
> ..or...
> 
>   =begin table width(10) height(9)
> 
>   =end table
> 
> ..or...
> 
>   =begin dialect Pod6
> 
>   =end dialect
> 
> I believe several parsers already allow this implicitly.

Or even explicitly. It's a feature of Pod::PseudoPod for things like:

=begin sidebar Title of the Sidebar
...
=end sidebar

And

=begin figure Caption for the Figure
...
=end figure

This made its way into Pod::Simple last year for Test::Inline. Sounds 
like Sean was in favor of it too:

   https://rt.cpan.org/Ticket/Display.html?id=16935

Allison