Re: require fails yet module exists in @INC path...?
- From: "Sisyphus" <sisyphus1@xxxxxxxxxxxxxxxxx>
- Date: Thu, 19 May 2005 17:18:16 +1000
"Chris" <newsbot@xxxxxxx> wrote in message
news:1116442508.603144.117180@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thanks for the tip on that. I'll look into doing this. Seems much
> simpler.
>
> But I'm not any further along on the other issue. I maintain that I am
> using require that correct way (though at one point I thought maybe I
> was not). I continue to be baffled because this isn't like the first
> time I've done a:
>
> eval qq{ require $class };
>
> where $class = "Some::Module::Name";
>
> And A1, A2, B1, and B2 work this way. C1 does not.
>
If $class contains a string like "Some::Module::Name" then I'm finding that
it's ok to do:
eval qq{require $class};
but not:
eval {require $class};
and not:
require $class;
The last 2 will inevitably complain that "Some::Module::Name" can't be
found.
The first will function as desired.
If you want to use either of the last 2, then $class needs to be a string
like "Some/Module/Name.pm".
Cheers,
Rob
.
- References:
- require fails yet module exists in @INC path...?
- From: Chris
- Re: require fails yet module exists in @INC path...?
- From: castillo . bryan
- Re: require fails yet module exists in @INC path...?
- From: Chris
- require fails yet module exists in @INC path...?
- Prev by Date: Re: Perl generated navigation menu
- Next by Date: Text parsing pb.
- Previous by thread: Re: require fails yet module exists in @INC path...?
- Next by thread: Welcome to my concise encyclopedia,thanks!!
- Index(es):
Relevant Pages
|