Re: Re: Re (tilly) 3: No excuses about not using CGI.pm

You got it in the wrong order. You can't execute a BEGIN block before you compile it, and you compile it in the order in the file. So you've compiled the lone mysub at the top, then you compile the first BEGIN block, then execute it, then compile the second BEGIN block, then execute it and OOPS! there's the problem.

Put the lone mysub at the bottom of the file, and it'll be all good.

-- Randal L. Schwartz, Perl hacker

[MeowChow]

Right, I was commenting on tilly's statement that reversing the order is a good way to silently ignore the prototype.

However, I wonder if the documentation in perlmod should be revised from:

A BEGIN subroutine is executed as soon as possible, that is, the moment it is completely defined, even before the rest of the containing file is parsed.

To something like:

A BEGIN subroutine is executed as soon as possible, that is, the moment it is completely defined, even before subsequent code is parsed, but after the code before it is parsed and compiled.

   MeowChow                                   
               s aamecha.s a..a\u$&owag.print

[merlyn]

I can't think of a time I would have expected it to be parsed before the code ahead of it is parsed. I mean, the compiler doesn't skip around willy-nilly in the source file!

Are you familiar with languages where the parser skips around? And if so, where does it skip to without, uh, parsing the file? {shrug}

-- Randal L. Schwartz, Perl hacker

[MeowChow]

Well, the operative words were "parsed and compiled".

   MeowChow                                   
               s aamecha.s a..a\u$&owag.print