On 10 April 2010 13:45, David Mertens <dcmert...@gmail.com> wrote: > I see no problems with that at all. Damian does, however. In PBP he mentions > that according to his own observations, when documentation is right next to > the function it is actually less likely to be edited.
I think you're extrapolating PBP beyond its original intentions here. Damian was discussing where pod should go *in the file*, and preferring all pod to go after __END__. AIUI, Gabor's idea was that it doesn't matter where it goes in the file: even if all the pod is at the end, Padre will find it for you anyway. That way, if you want to edit all the docs at once, you can go to the end of the file and get only docs. If you want to edit one function and its associated pod entry, you can use Gabor's proposed feature. And if you just want to tweak code without updating pod at all (because you're not changing observable behaviour or you're fixing bugs), you can just edit the code. Phil _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
