Are you implying the script isn't getting run?
No! I'm stating that how it gets run is of prime importance to the cause of the problem and its solution.
And that if you rely upon the windows "equivalent" of the unix shebang mechanism, it is enacted by the system shell, rather than by one of the system APIs. And that cannot be attributed to a 'bug' in windows, but simply a difference in the way the two platforms are designed to work.
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.
| [reply] |
I knew the script was getting run. My example was just as small a testcase as possible to illustrate what was happening. Adding the "$^X" inside the backticks solved the problem as you said. Of course, that's just the easy fix to running another perl script, but that's about all we do unless we're running an actual .exe of some kind (which falls into you're "binary so ok" category).
Thanks again!
Aaron | [reply] |