Re^3: Strict isn't strict enough (stop it)

... the docs seemed to be pretty emphatic that variable names should not be exported, so I was using full qualification instead.

But the variables the Exporter docs warn against exporting are package variables (AFAIU, the only variables that can be exported by the module in question), i.e., global variables, which are commonly acknowledged to have the potential "horrible effects at-a-distance" also referred to in the docs.

Your OPed question seems to boil down to "How can I use global variables without endangering my sanity?". The generally accepted short answer is "You can't!". (Remember: There is no Sanity Claus.)

Comment on Re^3: Strict isn't strict enough (stop it)

Replies are listed 'Best First'.
Re^4: Strict isn't strict enough (stop it) by davies (Monsignor) on Dec 31, 2011 at 19:12 UTC
You are right in thinking that I am concerned with global variables. I don't have a problem with using global variables for things that genuinely are global. Typically I read or generate these at the start of my code and then never change them, so I'm not particularly concerned for my sanity in that regard. I intended my OP question to be along the lines of "how do I avoid typos creating global variables I didn't want". If I can't do that, I have genuine fears for my sanity. :-) Regards, John Davies	[reply]
Re^5: Strict isn't strict enough (stop it) by roboticus (Chancellor) on Jan 01, 2012 at 06:57 UTC
davies: Then I'd use the reply from tye using Exporter. It'll let you mark the globals you want to be accessible, and then let you import them into the local namespace. If you typo it, then you'll get a message to the effect that "module foo doesn't export variable bar". ...roboticus When your only tool is a hammer, all problems look like your thumb.	[reply]