|There's more than one way to do things|
No, it's not my bug... it's a design failure in the language.
It is not said in the expert books on perl that you *must* put things in separate files. That's a made up requirement by people who didn't know or don't know how to call a bug a bug or work around it.
Fortunately, newer language constructs like 'use base' which says:
Now if you HVE to put things in separate files, why would could be going into the base that is specifically designed for when things aren't in separate files -- Why? Because perl wasn't designed to have the requirement that different classes be developed in separate files.
The fact that this does not work:
Is a bug in perl.
I try multiple ways, above to import that var. None of them work.
That doesn't mean you couldn't write various parts in BEGIN, but none of the introductory books written by the language authors say you should use BEGIN or separate files. To me -- that indicates that BEGIN's and separate files should tend toward being a more advanced topic -- while development of programs in 1 file should be considered the norm -- unless you want to break out functionality for use with other programs.
You shouldn't need to break apart a program if you are not trying to make libraries and if the program isn't getting "too long".
What is too long?
Taking perl as an example -- there are 147 "c" files in the 5.14.2 dist w/a total of 217508 lines. That's an average of 1500 lines/file. Most are small fails, but the meat of the main program is in large files.
In other projects 1500-3000 is not atypical for a single program -- with smaller files usually being library functions.
That people should think that breaking apart programs into little files is 'normal', goes against the norms of other languages.
I'm not certain, but I **think** (not sure) the only other language that might have such a similar requirement is 'java', the "Cobol" of the Web age.
I wouldn't call that a positive selling point.