in reply to Re: How to test if a file is readable on Win64?
in thread How to test if a file is readable on Win64?

I'm puzzled. Why would an eval make any difference?
  • Comment on Re^2: How to test if a file is readable on Win64?

Replies are listed 'Best First'.
Re^3: How to test if a file is readable on Win64?
by Anonymous Monk on Mar 10, 2014 at 23:58 UTC

    No, eval wouldn't make any difference

    If the -r test is causing the popup Win32API::File::SetErrorMode(2); should silence it

Re^3: How to test if a file is readable on Win64?
by jellisii2 (Hermit) on Mar 11, 2014 at 16:55 UTC

    It's my understanding that wrapping code in an eval will effectively fork and return the result code, setting $@ on an error. It should sidestep the crash nicely allowing for the catch that the OP appears to be digging for.

    That said, I could be answering the wrong question.

      eval never forks
      eval cannot trap win32 messageboxes (popups)
      win32 messageboxes (popups) are generated by msvs c-runtime ... they are not the result of die
        And thus ignorance continues to be quashed one post at a time. Thanks for this.