in reply to eval "require $class" seems wrong

eval { require $class }; :-)

update:

eval { require "$class.pm" }; :-)

Replies are listed 'Best First'.
Re^2: eval "require $class" seems wrong
by rvosa (Curate) on Aug 22, 2007 at 17:43 UTC
    That's not the same thing! Compare: 
    perl -Mstrict -e 'my $c="CGI";eval "require $c";die $@ if $@'
perl -Mstrict -e 'my $c="CGI";eval {require $c};die $@ if $@'

    [download]
[reply]
[d/l]
Re^2: eval "require $class" seems wrong
by rvosa (Curate) on Aug 22, 2007 at 18:03 UTC
    Ah, the update works. I'd ++ that if I had votes left for today :)
[reply]

      Then you are violating a different "best practice": Modules should always have a "::" in their name.

      - tye        

[reply]
        Okay, well, so in the general case (including '::' in module names), the non-string-eval way to do it seems to be: 
        
# turn $class name into $path
my $class = 'Some::Class';
my $path  =  $class;
$path     =~ s/::/\//g;
$path    .=  '.pm';

# check if $path already loaded
if ( not exists $INC{$path} ) {

    # do block eval on $path
    eval { require $path };
    die "Can't load $class: $@" if $@;
}

# if we make it here, we can use $class
my $obj = $class->new;

        [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom