Jay Savage <[EMAIL PROTECTED]> wrote: On 1/11/07, hOURS wrote: > > > Jay Savage wrote: On 1/11/07, hOURS wrote: > [snip]
> Thanks Jay. I can't believe I didn't think of that myself. I put in the > 1;'s and the "or die". It's not that the requires are failing - I get the > same results. I added > print $@; > right after the eval block. Each time, that reads "The Unsupported function > alarm function is unimplemented at line 5." What does that mean? > Fred > That means you don't have an alarm function, which probably means you're on Windows (AFAIK everything else implements a system alarm). If that's the case, you need to stop before you write any more code and read the perlport and Win32 manpages cover to cover. Then go take a look at the docs for the Win32 and Win32::Process modules. Doing that now will save you a lot of frustration later. You may also want to pick up a copy of Learning Perl on Win32 Systems. Since Windows doesn't implement an alarm function, you're probably going to need to rethink your approach: timing out require isn't really a viable option. Take a look at the combination of create and wait from WIn32::Process. HTH, -- jay -------------------------------------------------- This email and attachment(s): [ ] blogable; [ x ] ask first; [ ] private and confidential daggerquill [at] gmail [dot] com http://www.tuaw.com http://www.downloadsquad.com http://www.engatiki.org values of รข will give rise to dom! Wow. Is windows such a rarity in the PERL world that no one thought of it 'til now? Yes, that would in fact be my problem. The rest of your message is pretty much foreign language to me though. And reading something cover to cover sounds daunting. I just need a way to do this one thing. Does anybody have any coding suggestions for a Windows user who may end up making requires to programs with infinite loops? Thanks, Fred --------------------------------- Have a burning question? Go to Yahoo! Answers and get answers from real people who know.
