If you are using our to access data within one package only, why are you making it a global when you could trivially make it a lexical?I don't do that, and I didn't mean to imply that I did.
Here are the rules I follow. I use my unless there is a specific reason not to. I will use our for certain standard globals that need to be global, such as @EXPORT_OK. When I need to share variables across multiple files I try to use Exporter to export it from one place to all of the places that need it.I'm with you so far.
If that solution won't work, then I will "use vars" for the declaration. I never use our for any variables that I've invented within my code. ...I really don't see why you'd make that distinction. I just use our() for all package variables.
In reply to Re^7: My globals are visable; but undef'ed
by Joost
in thread My globals are visable; but undef'ed
by Wiggins
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |