Joshua ben Jore wrote: > On 6/11/07, Michael G Schwern <[EMAIL PROTECTED]> wrote: >> Joshua ben Jore wrote: >> > It has two benefits. Separating code from pod prevents it from being >> > wholely unreadable without syntax highlighting. >> >> <snip> >> >> > The other benefit is you don't spend the CPU parsing that additional >> > bit of text. I recall noticing it on some really pod-heavy code. >> >> The former is arguable. The latter is a commonly held misconception. >> Here is >> how perl "parses" POD: when in code it looks for a /^=\w+/ outside of a >> statement, everything following is ignored until it hits a /^=cut$/ or >> eof. >> The end. > > I think when I'd noticed it I'd been doing it to code that was 2/3 > pod. So no, not "the end." Just most of the time.
AFAIK there's no POD parsing code in perl beyond what I mentioned above. Take a look in toke.c, if you dare. > I guess I should > have just not even mentioned that I'd noticed it made a difference for > me if that's what it takes to avoid being told I'm wrong. Sometimes you're wrong. Its ok. You don't lose any points and we won't fine you. I'm wrong all the time. I could be wrong right now. If you've got that code around where you noticed a performance drop off from inline POD post it and we'll run it through its paces to see what's really going on.
