Use my instead.

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Using 'my' in this situation though would require that i pass that value on to the next sub routine wouldnt it? for example:

#!/usr/bin/perl -w
use strict;
&one;
sub one {
  my $a = "hello";
  &two($a);
}
sub two {
  my $a = shift;
  print $a;
}
[download]

i ask simply because this whole exercise is being done for a rather lengthy script i have that makes use of several subroutines, all called from one main sub. i end up passing a fairly long group of variables to each of the other subs

sub execute {
  &ccCopy($source,$destination,$host,$error);
}
sub ccCopy {
  my $source = shift;
  my $destination = shift;
  my $host = shift;
  my $error = shift;
}
[download]

this works, but i was hoping to use 'local' two get rid of these extra lines and try to streamline a bit.

humbly -c

The reason that local causes strict to complain is that local does not declare global variables (strict only complains about global variables if you haven't declared them). The purpose of local is to temporarily hide the original value of the global, so that you don't accidentally overwrite a value that the rest of your program is using. Basically, letting you use a global variable as if it were lexical. (Sort of.)

However, that's not what you want to do. You actually want to access the global value of the variable but you want to declare it, so that strict stops complaining. To do that, remove the locals, and add an our (or use vars for < 5.6) to the beginning of the program:

#!/usr/bin/perl -w

use strict;

our $i;       # Predeclare $i as a global, so
              # that strict doesn't complain.

my @array = qw(one two three);

&one;

sub one { 
  foreach $i (@array) {
    &two;
  }
}

sub two {
  print "$i\n";
}
[download]

That said, global variables are usually a bad idea, especially in large (or "lengthy") programs. You should probably go with dragonchild's hash suggestion, or something.

bbfu
Seasons don't fear The Reaper.
Nor do the wind, the sun, and the rain.
We can be like they are.

Why not try something like:

sub execute {
    my %argsHash = (
        Source => $source,
        Dest => $destination,
        Host => $host,
        Error => $error,
    );

    &ccCopy(\%argsHash);
}

sub ccCopy {
    my $args = shift;

    print "Copy: $args->{Source} to $args->{Dest}\n";
}
[download]

That will do two things:
1. Clean up your messy-looking code
2. Make it so you stay out of procedural messes by fooling with global variables. (They're sorta like matches, but for big kids. You still don't want to play with them.)

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Hi c,

In my opinion your comment that this "is being done for a rather lengthy script" says to me that you want to avoid globals at all cost. The comments and snippits of advice of our fellow monks in this case are excellent and will work perfectly fine for you. But just in case you were looking for yet another way to do it...

Read more... (2 kB)
--
http://www.nule.org

But as and aside regarding use vars and  our declarations. I don't believe they are quite equivalent. This might be splitting hairs, but a use vars declaration gives a package variable while an our declaration gives a global disguised as a my variable. This means the scoping is lexical for our variables. The following code

&decl();
print $variable;
sub decl {
    our $variable = 1;
}
[download]

Another implication, if you are using packages to give different name spaces in the same file, a declaration like...

package one;
use vars qw($thing1);
our $thing2;
#stuff;
package main;
print "$thing1 and $thing2";
[download]

I didn't get this when I first started using <cod>our</code> so I just wanted to throw it there since it seems to apply to this thread.

Ira,

"So... What do all these little arrows mean?"
~unknown

$::i       # implicit, 
$main::i   # explicit
[download]

#!/usr/bin/perl -w

use strict;

my @array = qw(one two three);

&one;

sub one { 
  local $::i;
  foreach $::i(@array) {
    &two;
  }
}

sub two {
  print "$::i\n";
}
[download]

#!/usr/bin/perl -w

use strict;

my @array = qw(one two three);

one();

sub one { 
  foreach (@array) {
    two($_);
  }
}

sub two {
  print "$_[0]\n";
}
[download]

TIMTOWTDI :)

cLive ;-)