I usually place synopsis at the beginning of the file, function descriptions right above functions and the rest after the __END__. For me it's convenient and I don't find this ugly.
If you doesn't like this style and want to place all POD after the __END__ it shouldn't be a problem. Most of editors (though I actually familiar only with Vim ;) allows to split file and see its different parts simultaneously. Also folding may be helpful if you don't want to see long functions' descriptions.
Approach with auto-copying looks somehow strange for me. Do you suggest to move function descriptions to the end of the file before closing and move them back just after opening? It doesn't make sense. If you do not plan to move descriptions back, then why not to place them in the end of the file since beginning?
In reply to Re: POD using __END__ with function comments
by zwon
in thread POD using __END__ with function comments
by zerohero
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |