On 14 Mar 2005 at 9:49, Schupp Roderich (extern) Com wrote:
> Hi,
> putting pp packing instructions into POD
> is definitly a good idea!
>
> > > On the other hand, why not process the "=item PAR
> > --addlist" into multiple "--addfile"
> > > options and avoid the extra file? It's equivalent.
> >
> > This is a nice idea. I'll look at doing just that. The
> > --addlist option is the only argument specialisation at the
> > moment anyway.
>
> What about bracketing the whole pp stuff into
>
> =begin pp
>
> ...pp information, format TBD...
>
> =end pp
>
>
> Cheers, Roderich
I was also thinking that way. However, =head2 shows up in the output of
translators
like pod2html, whereas =begin and =for do not show up. Treating that as a
feature, I
was thinking there should be four cases:
One liners that show up in translation
=head2 PAR -c -l filename1 -l filename2 -a filename3 -filename4 -o
my_app
Multiple liners that show up
=head2 PAR
-c
-l filename1
-l filename2
-a filename3
-a filename4
-o my_app
=comment some other pod command
One liners that are not visible in translation
=for PAR -c -l filename1 -l filename2 -a filename3 -a filename4 -o
my_app
and multiple line non-visible ones
=begin PAR
-c
-l filename1
-l filename2
-a filename3
-a filename4
-o my_app
=end
I'm undecided about "=head2 PAR" vs "head2 pp" as well as accepting
/=head[1234] (PAR|pp)/.
I don't think "-A" as a special case embedded list needs to be there, since it
is just
as easy to use multiple "-a" instead.
I would suggest also that the -O (capital O) be the pp option that makes it
look for
embedded pod options and that any other options on the command line with -O
override
anything found embedded for any single value option such as "i", "o", "v", "T",
or "z",
and additive for the others.
I also started doing some coding, but I am going on a couple weeks vacation and
won't
pick it up again till I get back. Robin, if you would like to do it, go for it.
Alan Stewart
