Re: Are many use statements a code smell?

I do not think there is something wrong with much use statements. As long as every of the modules has a independent usage/sense without the others.
Otherwise you could refactor it into one module with subclasses.

Stu::AddressBook
Stu::AddressBook::Account
Stu::AddressBook::Email
...
[download]

where Stu::AddressBook use the other module parts and your script just start with

use Stu::AddressBook;
my $ab = Stu::AddressBook->new;
[download]

Boris

Comment on Re: Are many use statements a code smell? Select or Download Code

Replies are listed 'Best First'.
Re^2: Are many use statements a code smell? by crenz (Priest) on Jun 18, 2005 at 00:24 UTC
And Stu::AddressBook could do something like `use Module::Find; useall Stu::AddressBook::Plugins;` [download] which uses Module::Find (caveat: I wrote it ;-)) to find Stu::AddressBook::Plugins::Account, Stu::AddressBook::Plugins::Email, and so on.	[reply] [d/l]