Regardless of any contortions Benchmark goes through to execute code in the calling package, lexical variables are not in any package. It is impossible for code to access lexical variables that are not in scope.

No arguments here. My only problem with your post was the line I quoted. I've just reread your original post and you have to admit its a little ambiguous. Yes the code is executed inside of the _file_ Benchmark, but not in the package Benchmark. And this leads to an interesting point (about which Ill have to trawl the docs for at a later time) the two are different. Consider the below code

#Put in file TestA.pm in a root lib directory
package TestA;
my $var="TestA";
1;

#Put in file TestB.pm in a root lib directory
package TestB;
use TestA;
my $var2="TestB";

package TestA;
print "'$var','$var2'";
1;
[download]

Now if you do perl TestB.pm you will see

'','TestB'
[download]

But if you stick the entire code snippet into TestB.pm then you will see

'TestA','TestB'
[download]

Even though you might expect that the lexical variable $var would be out of scope.

_{(Incidentally I have a development Lib directory that I use for this type of stuff and have my enviornment configured to always include it.)}
Update
It seems to me the moral of this is that when you put many packages in a single file everything following the package declaration should be placed into an anoymous block. Ie:

package TestA;
{
  my $var="TestA";
  1;
}

package TestB;
{
  use TestA;
  my $var2="TestB";
}
package TestA;
{
  print "'$var','$var2'";
  1;
}
[download]

Yves / DeMerphq
--
Have you registered your Name Space?