I appear to be the world's only user of interlaced pod.
If I can't get any feedback on whether =head2 would be useful, can I at
least hear any objections or counter-examples to adding =cut into the
mix? This at least allows interlaced pod with the '=item' form.
--- /tmp/Base.pm 2007-02-18 12:21:58.000000000 -0800
+++ /tmp/Base.pm2 2007-02-18 12:23:14.000000000 -0800
@@ -1881,7 +1881,7 @@
while (<$fh>) {
if (/^=item\s+\Q$action\E\b/) {
$found = 1;
- } elsif (/^=(item|back)/) {
+ } elsif (/^=(item|back|cut)/) {
last if $found > 1 and not $inlist;
}
next unless $found;
(In case it's not obvious yet, I've got about 3 changes to Base.pm
sitting here and they're getting in the way :-)
# from Eric Wilhelm
# on Wednesday 17 January 2007 04:47 pm:
> # various other actions
>
> =back
>
> =cut
>
> # all supporting (non ACTION_*) code has to be down here
>
>Ok, but now ./Build help foo prints the source for the foo subroutine!
>(And actually, all of the source until it sees another /^=(item|
>back)/.) That's a little more help than I wanted.
>
>This can be made to work by simply adding =cut into the stop
> condition. However, =item entries do not show up in the index at
> the top of most htmlized pod (and one could rightly argue that they
> shouldn't.)
--
software: a hypothetical exercise which happens to compile.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
