Does this make sense or is my blood sugar too low?

Well... I am getting at his module via:

use Package

Package::get_data();
[download]

yet mysteriously in my code after I call Package::get_data() all of a sudden I have variables $x, $y, $z that are defined... now I would have expected theses variables to be Package::x Package::y Package::z, but there they are. I asked the engineer about this and he said that there wasn't any other way to pass multiple variables back through a return... when I suggested a hash he was particularly receptive to the idea...

untested psuedo-code

use strict; # To make sure you use the right package names.
package My_Wrapper;
sub My_get_data 
{ 
    local $x, $y, $z; # I had 'my', but [tilly] is right.
                      # Thats why I said, "I think." here.
    get_data( @_ );
    return ( $x, $y, $z );
}
package My_main
my ( $x, $y, $z ) = My_Wrapper::My_get_data;
[download]

That's a stab in the dark. I'm tired and I don't feel like taking the time to construct your situation for testing. But I think that is the direction to go. My_Wrapper will collect ugly globals, but they shouldn't propogate to My_main.

Instead I've gotten professional help ;)... which is cool, 
but I'm a *lowly* contractor here *and* too
young... hrmmm... so I can't really get in and play the 
political games to actually fix the problem correctly...
I've bugged the guy a few times to help him fix some 
things, but he's a little put off by having some 'green'
punk kid teach him anything. If anything I think it 
bothers him more that I've been programming longer than
him... and more than likely getting paid more. :(


###########

This is precisely the culture that I work so hard to avoid,
yet landing there seems to be unavoidable.  

If you have a valid point ( and it looks like you do based
on your description of the problem ), then I suggest you
become an evil, manipulative bastard by asking the following
question:

"What am I missing?"

This insidious little question is extremely confrontational
because it forces them to explain to YOU exactly how their
way will work.  Their explanation will not make sense, so
be sure to ask it in the presence of at least 1 ally.  If
they dodge, repeat the question.

If they dodge, repeat the question.

If they dodge, repeat the question.

If they dodge, repeat the question.

If they dodge again, say "Excuse me, but I really do not
understand what you are doing here.  Can you please help
me understand what you are trying to do and how I can
succeed with your code?"

If they don't help you, then that is a refusal to help
a coworker whose work depends upon their success.  At that
point, maybe some sort of third party intervention shall 
be required.  Be sure to present it as in the context of
how you do not understand what the other person is doing and
they are refusing to work with you to solve the problem.

Also, be prepared to leave if your company is extremely sick
culturally.  They will not like this.  Having allies 
present is extremely important.  This is a CYA for your
presentation to HR...if 3 people complain to HR, it will 
probably be believed.  If 4 people complain to HR, it shall
be believed and action will be taken.

##########

On a lighter note:

while ( $dodge ) {

   print "What am I missing?\n";

} # while

--moo