> BEGIN blocks do not take precedence over one another--they are all > still executed. They are, however, executed immediately after perl > finishes compiling them. So, if you have the following code:
Ok, so I'm guessing that the reason that 3214 is displayed is not because of precedence, but that every begin block is pushed into a stack of some kind, and when perl starts executing code, code on the top of the stack ends up being run first. Is that right? So it's sort of like precedence but really isn't. Which explains when things printed off are printed off from innermost begin to outermost begin, but a subroutine declared in a begin nested in other begins creates an error when called before the sequence in the code. Correct? -Dan -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
