Front page | perl.perl5.porters |
Postings from February 2013
On 24 February 2013 22:25, James E Keenan via RT <perlbug-followup@perl.org> wrote: > On Sat Aug 22 11:45:29 2009, ikegami@adaelis.com wrote: >> On Sat, Aug 22, 2009 at 7:44 AM, Rafael Garcia-Suarez < >> rgarciasuarez@gmail.com> wrote: >> >> > 2009/8/21 Aaron Trevena <perlbug-followup@perl.org>: >> > > Adding pod inside of a function call resulted in the following >> error: >> > > >> > > String found where operator expected at >> > > >> > >> > /home/teejay/development/freelance/lucemincendo/trunk/webserver/script/../lib/RSTDB/Schema/Result/Person.pm >> > > line 30, near "cut >> > > "person_id"" >> > > (Do you need to predeclare cut?) >> > > >> > > It appears that perl parses the =cut at the end and the next line >> as >> > > code, rather than just the next line - adding whitespace and >> newlines >> > > didn't affect this. >> > >> > I think that this is documented somewhere (you can use pod only >> > between statements), but I can't find where exactly by now... >> > >> >> It's in perlsyn. It needs to be in perlpod as well! > > No patch was ever submitted for this ticket, which was filed more than > three years ago. Yes - so long ago I'd forgotten it :) > Do people feel a patch is needed? (I myself am doubtful.) Can someone > produce a patch? I can write a doc patch (about the limit of my ability to contribute to perl-core) if it would help - perlpod would seem an appropriate place to mention you shouldn't put pod in places like that - if it would make the perlpod docs overly verbose I'm happy to leave it and for the ticket to be closed. To be perfectly honest, it's just something I noticed while picking a tidy way of laying out DBIC classes, it's not something I'd do again (and haven't in the last 5 years). Cheers, A -- Aaron J Trevena, BSc Hons http://www.aarontrevena.co.uk LAMP System Integration, Development and ConsultingThread Next