in reply to Problems sometimes loading File::Glob

... isn't glob and even just @files = <*.*> a builtin? Is that wrong? Oh! It says right on the page I linked that glob is the angles and that they are File::Glob. I was not aware of that.

Do you have more than one perl installed? Personally, I'd reinstall perl if I discovered a corrupted core dll like that. To hells with feature freezes or whatever. That'd be a serious stability issue.

UPDATE: based on shmem's musings... If you pop open that dll, does it have win32 headers in there? Is it in fact corrupted in some way?

-Paul

Replies are listed 'Best First'.
Re^2: Problems sometimes loading File::Glob
by HuckinFappy (Pilgrim) on May 23, 2007 at 18:18 UTC
    Yes, it is a builtin, but: 
    10] perldoc -f glob
       glob EXPR
       glob    In list context, returns a (possibly empty) 
               list of filename expansions on the value of 
               EXPR such as the standard Unix shell /bin/csh 
               would do. In scalar context, glob iterates 
               through such filename expansions,
               returning undef when the list is exhausted. 
               This is the internal function implementing 
               the "<*.c>" operator, but you can use it directly. 
               If EXPR is omitted, $_ is used.  The "<*.c>" 
               operator is discussed in more
               detail in "I/O Operators" in perlop.

               Beginning with v5.6.0, this operator is 
               implemented using the standard "File::Glob" 
               extension.  See File::Glob for details.

    [download]
    So the builtin glob calls load the File::Glob module on the fly apparently
[reply]
[d/l]
Re^2: Problems sometimes loading File::Glob
by HuckinFappy (Pilgrim) on May 24, 2007 at 14:25 UTC
    One perl installed. There is nothing wrong with the .dll itself. I've compared checksums of the .dll on 20 different machines, and they all match. And keep in mind, this loads and works fine 99.99% of the time.

    I've learned something new here, putting an eval block around the glob does nothing. Apparently the compiler sees the glob at compile time, and goes off to load the File::Glob module at that time.

    So now I'm faced with a different issue that I may form as another SoPW Thanks,
    ~Jeff

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom