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

eval the test:

eval {-r "$File1"};
if ($@) { 
    $Debug && print "File $File1 is not readable!  Return was $@.\n"; 
    return 1;
  }
[download]

Comment on Re: How to test if a file is readable on Win64? Download Code

Replies are listed 'Best First'.
Re^2: How to test if a file is readable on Win64? by rhardy (Acolyte) on Mar 10, 2014 at 23:52 UTC
I'm puzzled. Why would an eval make any difference?	[reply]
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	[reply]
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.	[reply]
Re^4: How to test if a file is readable on Win64? by Anonymous Monk on Mar 12, 2014 at 11:00 UTC
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	[reply]
Re^5: How to test if a file is readable on Win64? by jellisii2 (Hermit) on Mar 12, 2014 at 11:24 UTC