For those not familiar with the title phrase: CodeSmell
Although IMO "Are many use statements a code smell?" might be a better title.
And to add an answer, usually when ive had to do this i usually end up putting all the use statements in the root class. So the client says
use Stu;
And all the subclasses are pulled into memory. But i dont have startup time constraints. Its fine for my code to chug a little on startup as it usually runs for hours anyway. YMMV.
In reply to Re: Are many use statements a code smell?
by demerphq
in thread Are many use statements a code smell?
by rlb3
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |