in reply to use vs. require in string eval?

Isn't the whole point that use happens at compile time and require happens at run time. You can only benchmark run time behaviour...

So your eval "use $object_class"; is effectively trying to benchmark nothing except the eval overhead itself - which in this case is efectively nothing.

use is a declaration - require is a function - confusingly both are in the functions listed in chapter 3 of the camel book.

I would thus suspect that eval "use $object_class"; is actually wrong.

+++++++++++++++++
#!/usr/bin/perl
use warnings;use strict;use brain;

Replies are listed 'Best First'.
Re: Re: use vs. require in string eval?
by PodMaster (Abbot) on Mar 12, 2004 at 04:32 UTC
    It doesn't matter if "use" is a declaration, eval happens at runtime, and things that happen inside of string eval happen when eval happens.

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
Re: Re: use vs. require in string eval?
by lachoy (Parson) on Mar 12, 2004 at 04:40 UTC

    I actually suspected this as well, but all the tests for Class::Factory still ran okay. If the 'eval "use..."' worked out to a no-op they would have failed all over the place.

    Chris
    M-x auto-bs-mode

[reply]

In Section Seekers of Perl Wisdom