Re^2: Auto-evaluating anonymous subroutines

There's no need to put your @EXPORT and *import assignment in a BEGIN block. File-level code in modules is run just after it's been compiled. It's where the required "true" value comes from. That is, if Character uses AutoExecute, the work required to set up Exporter has already completed by the time AutoExecute->import() is run. You only need to use a BEGIN block if other code in the same module cares that your snippet runs before later code in the same file is compiled.

⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

Comment on Re^2: Auto-evaluating anonymous subroutines

Replies are listed 'Best First'.
Re^3: Auto-evaluating anonymous subroutines by ikegami (Patriarch) on Feb 21, 2006 at 03:25 UTC
There's no need to put your @EXPORT and *import assignment in a BEGIN block. Oh I realize that. If you read Re: Undefined subroutine errors and Re^3: Undefined subroutine errors, you'll see that not only do I understand execution order quite well, I placed those statements in BEGIN block for a reason: that pattern allows two modules to include each other. Obviously, that's not required here, but I don't see any reason why I shouldn't use the pattern here. By the way, I also explain execution order in Re: BEGIN and END blocks, use strict and scoping.	[reply]
Re^4: Auto-evaluating anonymous subroutines by diotalevi (Canon) on Feb 21, 2006 at 03:36 UTC
I'm ttrying to think of the last time I wrote modules that used each other. A few years? They were OO and didn't use Exporter either. ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊	[reply]