Re: Sharing Namespaces

use One;
use Config;

my $config = Config -> new();
my $one = One -> new();

if ($one -> can('config') {
  $one -> config($config);
}
[download]

There's one.

Comment on Re: Sharing Namespaces Download Code

Replies are listed 'Best First'.
Re^2: Sharing Namespaces by skazat (Chaplain) on Jan 27, 2006 at 09:19 UTC
erm, ok, what's $config? A reference to a variable? A typeglob... what? At the moment, the Config.pm module isn't an OO bit of code, it's just a list of variables, basically - that's why I was interested in exporting the entire namespace (sorry if that wasn't clear - my bad) -justin simoni skazat me	[reply]
Re^3: Sharing Namespaces by gloryhack (Deacon) on Feb 01, 2006 at 12:28 UTC
Upon re-reading, it's perfectly clear that your Config.pm is a data store... the lack of clarity was all on my end. I have a possibly irrational aversion to allowing modules to pollute my namespace, so were it mine to do I'd subclass Config.pm to provide an interface layer and work toward phasing out the legacy version over time.	[reply]