Re: Are many use statements a code smell?

[borisz]

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
...

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

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

[crenz]

And Stu::AddressBook could do something like

use Module::Find;

useall Stu::AddressBook::Plugins;

which uses Module::Find (caveat: I wrote it ;-)) to find Stu::AddressBook::Plugins::Account, Stu::AddressBook::Plugins::Email, and so on.