rjbs/pod-elemental-perlmunger — pull request #2 by madsen (2012-07-09 23:39:34+00:00)
Title: Place POD after __END__ if possible

Right now, if the source document contains `__END__`, PerlMunger will always place the munged POD before the `__END__` marker, even if there was nothing after the marker except POD and/or whitespace.

This change, adapted from Pod::Loom, detects that case and discards the useless `__END__` section, allowing it to place the POD after `__END__` (so it doesn't have to be read when the module is loaded). Documents with a `__DATA__` section (or something other than POD after `__END__`) will continue to get the munged POD placed before the `__DATA__` marker.

Also, I added some tests.