I was kinda suggesting the best practice was to avoid requireing dynamic class names completely, and address the problem at a higher level.
To answer your question directly, one can require either a class supplied as a bareword or a path. There isn't a way to require a class supplied in a scalar. In order to load a dynamically constructed class name, some use eval EXPR to do the former (e.g. Module::Pluggable), and some transform the class name into a path and use the latter (e.g. if). I have no idea why one cannot do require $class;.
In reply to Re^3: eval "require $class" seems wrong
by ikegami
in thread eval "require $class" seems wrong
by rvosa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |