Thanks, GrandFather, for your response. I appreciate it very much. As with all the other responders, your wisdom always helps me to grow.
I posted an update to my node and included, as most of the responders wisely suggested, a block of code to illustrate what I am inquiring about. It is not, of course, the full code; but I think it highlights in a way that portrays what I am doing.
I am including in $entry the full directory path specification, so I'm not clear on why the test would fail if I'm executing the code in a directory different from the one I'm trying to process. But I presume I'm not actually doing what I think I am doing...which is what has me perplexed.
I am confident that the -d filetest operator is working properly and that it works just fine on Windows (as you most appropriately noted from your own experience). So I'm likewise confident that I'm doing something wrong.
As I noted in response to another's monk's response, I've tried the code through the debugger and $entry checks out with the proper full path specification. And, of course, I can't see with the debugger what the -d function thinks it is seeing other than the value of $entry. It does, of course, also confirm that it is the }else{ clause that gets executed.
In reply to Re^2: Directory checking on Windows XP
by ack
in thread Directory checking on Windows XP
by ack
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |