Re^3: unlink fails to delete files with perculiar names

It's merely speculation that he assigned it using a double-quoted literal

Agreed. That's why likely work.

It might just as well have come from a readdir

But don't you have to combine the values from readdir with the path in order to get a fully qualified path?

Could he be doing something like $targ = "$path/$fname";?

why would unlink have returned 1, as the OP states?

Not sure, but that construct looks suspect to me: my($no) = unlink $targ || carp "Unable to delete file $targ\n";.

What ends up in $no if unlink returns 0; the return value from carp()?

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^3: unlink fails to delete files with perculiar names Select or Download Code

Replies are listed 'Best First'.
Re^4: unlink fails to delete files with perculiar names by Anonymous Monk on Nov 22, 2011 at 11:06 UTC
Yup `$ perl -MCarp -e " my $f = unlink (666) \|\| carp 1; die $f " 1 at -e line 1 1 at -e line 1.` [download]	[reply] [d/l]
Re^5: unlink fails to delete files with perculiar names by Eliya (Vicar) on Nov 22, 2011 at 12:11 UTC
No, because the OP didn't use parentheses with the unlink call, so the carp doesn't even execute. `$ perl -MCarp -e ' my $f = unlink 666 \|\| carp 1; die $f ' 0 at -e line 1.` [download] (see Re: unlink fails to delete files with perculiar names)	[reply] [d/l]