Re: scoping across parent/child relationship

[demerphq]

geektron: the variables declared in the child process are only used in sub Initialize and in sub do_child_stuff, so I would think that the scope is valid... Nope. Other people have explained why so I wont comment. But I was wondering why you dont pass them as parameters to the functions? Then scoping doesnt become a problem:

    my ( $foo, %bar, $bax );

    Initialize_child($foo,\%bar,$bax);
    do_child_stuff($foo,\%bar,$bax);

or with named parameters:

    sub Init_Child {
        my %params=@_;
        #blah
    }
    Init_Child(name=>$foo,attribs=>\%bar);

Yves
--
You are not ready to use symrefs unless you already know why they are bad. --tadmc (CLPM)

[geektron]

But I was wondering why you dont pass them as parameters to the functions? Then scoping doesnt become a problem

because i need them in both subs, and the actual variables are ( rather large ) config hashes. they can be global to the child ( if that makes sense )....

just trying to get the most out of laziness...

[demerphq]

Sorry but thats not a good reason. Pass them by reference, or in a hash, or even create an object that bundles them all together into a nice package.
Globals vars are evil without very very good justification. There is almost always an easier and safer way to do things.
Almost the only time I use them is for things like a $Debug variable in a package.

OTOH, its your code.... :-)

Yves
--
You are not ready to use symrefs unless you already know why they are bad. -- tadmc (CLPM)

[rchiav]

Then why not pass them as ref's?