in reply to Re^2: Executing perl program from another perl program and capturing the output
in thread Executing perl program from another perl program and capturing the output

I had tried Win32:GetShortPathName and it worked but, as this is a cross-platform tool, I prefer to avoid platform-specific code paths where possible.

Indeed. I don't have to write cross-platform very often, and I have no problem using well-written modules when required.

But unlike many others (it seems), my criteria for "when required" extends well beyond 'it exists'. If I don't need it, I don't use it(*).

I like simple! (Which my wife would probably say, is just as well ... :)

There are very good reasons for keeping ones dependencies to a minimum.

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: Executing perl program from another perl program and capturing the output

In Section Seekers of Perl Wisdom