On Friday 08 February 2002 04:24, Gregory Belenky wrote:
> | >God that's a toughie... I don't really know the answer, except maybe to
> | >check something like module->can('new') before trying to load it.
> |
> | Could it be a hard-to-find spelling error somewhere in the 'package',
>
> 'use', or configuration directives ? Smth like case error ? Bizzare results
> are often produced by such errors and they are extremely hard to fix.
>
>
> No. When I split module by packages - everything's fine.
> Just split and place in @INC dir-tree. No source changes.
>
> Gregory Belenky
> WebZavod (http://www.webzavod.ru) programmerWell, I've had equally weird things happen in Perl in the past. There has been a bug for instance lurking in perl since at least 5.004_03 that causes "my" variables to sometimes have improper scoping. Its very rare and only happens when you use deeply nested hierarchies of inheritance, but not even G. Sarathy was able to dope out WHY it happens! Once in a while you just have to bend to the inevitable, annoying as it is. > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
