Re: strict and variable scopes

An important thing to keep in mind, is that you are defining a lexical variable with my @in. This means it will only be in scope within that block, unless you use a method like flocto mentions above. Though it can be useful to subvert perl (sometimes essential?), one should always consider what is really trying to be accomplished and whether that subversion is truly necessary.

There may be a semantics problem here, too. One of the reasons that my was introduced to perl to was to give perl true local variabls, as local was a work around using a technique of substituting globals. What you would be telling perl is "please make this a local variable, but then don't be strict with me and let me use it anywhere I want without chiding me" (I hope that doesn't sound too harsh!). If you really want global variables, you probably want to use what perl terms as "package" variables:

Instead of using my, you would declare the package that you are in (probably just "main" in this case) like so:
$main::in = ...

Hope that helps. By the way, there are all kinds of nodes here discussing local, my, our etc., and how various monks deal with scoping. Best of luck!

Comment on Re: strict and variable scopes Select or Download Code

Replies are listed 'Best First'.
Re: Re: strict and variable scopes by Anonymous Monk on Mar 20, 2002 at 18:17 UTC
An important thing to keep in mind, is that you are defining a lexical variable with `my @in`. This means it will only be in scope within that block, unless you use a method like flocto mentions above. But if I call an external procedure, won't this procedure inherit the environment of it's caller - and therefor all of it's variables be within the scope of that very block?	[reply] [d/l]
Re: Re: Re: strict and variable scopes by chromatic (Archbishop) on Mar 20, 2002 at 21:07 UTC
Short answer: No, it won't. Long answer: It won't inherit lexical variables. That's the point. If you localize a global name, that change will be visible to all functions called within the scope of the change. That won't help you here, though, as you first need to declare a global name with the vars pragma.	[reply]