Macros whose first line starts with =head1 fail to load. about pg HOT 6 CLOSED

In my opinion this is not an issue. That is actually what is expected by Perl POD. Any of the POD directives (lines that start with =) should have and empty line before and after them.

This is caused because I removed the newline from the eval call. You will need to take your pick of what is more important. Do you want errors and warning reported at the correct line number in the macro file, or do you want this to work? In my opinion, this behavior is not important (particularly since it is invalid POD in any case).

from pg.

Note also that if you run perltidy on a Perl file that starts with a POD directive with no empty line before it (like =head), then it will add an empty line. You should run perltidy on your macro files anyway.

from pg.

I'm okay with this not being a real issue due to I'm using invalid POD. I just had multiple macros stop working for me that did work in 2.18 because I didn't realize there had to be a new line and it took me a while to figure out what the actual problem was with the macro files (the errors were strange but didn't actually point me to the issue with the POD). I may not be the only person who has custom macro files like this that may break in the upgrade from 2.18.

from pg.

I added a note to the release notes.

from pg.

Note that with pull request #962 the macro will compile, but a warning will be emitted.

from pg.

Fixed with #962.

from pg.