Okay, that makes sense. However, I just tried to create errors by deleting a) a non-existant subdir. b) a subdir which I did not have permission to delete. I tried this using eval as shown in your post and again in neither case did anything end up in $@. I did get various messages to STDERR: 

Can't make directory testtesttest read+writeable: Permission denied at
+ C:\test\QOTW\test.pl line 27
Can't read testtesttest: Invalid argument at C:\test\QOTW\test.pl line
+ 27
Can't make directory testtesttest writeable: Permission denied at C:\t
+est\QOTW\test.pl line 27
Can't remove directory testtesttest: Permission denied at C:\test\QOTW
+\test.pl line 27
and can't restore permissions to 0777
Should be no errors
$!: 'Permission denied'
$@: ''
Can't make directory testtesttest read+writeable: Permission denied at
+ C:\test\QOTW\test.pl line 31
Can't read testtesttest: Invalid argument at C:\test\QOTW\test.pl line
+ 31
Can't make directory testtesttest writeable: Permission denied at C:\t
+est\QOTW\test.pl line 31
Can't remove directory testtesttest: Permission denied at C:\test\QOTW
+\test.pl line 31
and can't restore permissions to 0777
Should be errors
$!: 'Permission denied'
$@: ''

[download]

Looking at the docs I saw this:

Note also that the occurrence of errors in rmtree can be determined only by trapping diagnostic messages using $SIG{__WARN__}; it is not apparent from the return value.

Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.

In reply to Re: Re: Re: My first thought was to build a macro... was I right? by BrowserUk
in thread My first thought was to build a macro... was I right? by princepawn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.