|No such thing as a small change|
Re^2: RFC: IPC::System::Simple under Win32by pjf (Curate)
|on Jul 11, 2007 at 06:14 UTC||Need Help??|
Tongue-in-cheek answers: Because having another module to do "system" doesn't actually make things simpler?
There's no denying that IPC::System::Simple is yet another wheel. It overlaps with a lot of the existing modules that handle calls to external commands. However it exists specifically to present the smallest possible learning curve for someone who wants to Do The Right Thing when calling external commands, but doesn't care how.
I can take someone who has almost no understanding of how Perl works, who has a full bladder, and a flight to catch in five minutes, and still teach them how to use IPC::System::Simple. I can do it in one slide in a classroom.
When I can tell people they can take their ugly, legacy Perl code, and replace each instance of system() with run() and suddenly get error checking and detailed diagnostics for free, that's a powerful force. If they want anything more than that, that's what all the other modules are for.
Because having yet another special case of how things work on Windows doesn't make things simpler?
I agree entirely! This is specifically making the module work the same way under Windows as it does everywhere else. Let's take your example:
And here's the crux of the problem. Currently, that does work fine under Windows. According to the documention in perldoc -f exec, it shouldn't:
Under Windows, Perl's system() is currently doing exactly what it shouldn't do, interpreting shell metacharacters and commands when called with multiple arguments. In my opinion, this is a bug in Perl.
So, I guess my real question should be this. At what point does IPC::System::Simple break bug-for-bug compatibily with Perl, and do what Perl says it should do, rather than what Perl actually does?
Perl Training Australia