Add Process.shell and Process.runShell.

sdk/lib/io/process.dart

Index: sdk/lib/io/process.dart
diff --git a/sdk/lib/io/process.dart b/sdk/lib/io/process.dart
index c1a060a556ffdba90ab40e2047814ff809df194a..381610a566159a17eb0e17a5af342c7f1d0167f6 100644
--- a/sdk/lib/io/process.dart
+++ b/sdk/lib/io/process.dart
@@ -99,6 +99,43 @@ abstract class Process {
                                             List<String> arguments,
                                             [ProcessOptions options]);
 

[Søren Gjesse, 2013/05/17 14:48:56]

This method needs a comment.

Should there be a way of specifying the actual shell command to use? Or should
we just document the search strategy used. See comments below.

[Anders Johnsen, 2013/05/22 07:45:51]

Done.

+  static Future<ProcessResult> runShell(String executable,
+                                        List<String> arguments,
+                                        [ProcessOptions options])
+      => run(_getShellCommand(),
+             _getShellArguments(executable, arguments),
+             options);
+

[Søren Gjesse, 2013/05/17 14:48:56]

I am not sure we should have both runShell and shell. The do almost the same. To
be consistent I think when something returns ProcessResult it should be called
runXXX.

[Anders Johnsen, 2013/05/22 07:45:51]

Done.

+  static Future<ProcessResult> shell(String command,

[kustermann, 2013/05/21 07:50:00]

What is this method doing?

[Anders Johnsen, 2013/05/22 07:45:51]

It's gone.

+                                     [ProcessOptions options])
+      => run(_getShellCommand(),
+             _getShellArguments(command, []),
+             options);
+
+  static String _getShellCommand() {

[Søren Gjesse, 2013/05/17 14:48:56]

Maybe we should do more extensive search of the shell to use.

[Anders Johnsen, 2013/05/22 07:45:51]

Done.

+    if (Platform.operatingSystem == 'windows') {
+      return "cmd";

[Søren Gjesse, 2013/05/17 14:48:56]

Should we lookup %COMSPEC% in the Windows environment? Should it default to
"%WINDIR%\system32\cmd.exe"?

[Anders Johnsen, 2013/05/22 07:45:51]

Done.

+    }
+    return "sh";

[Søren Gjesse, 2013/05/17 14:48:56]

Should we lookup $SHELL in the environment? Should it default to /bin/sh?

[ricow1, 2013/05/21 07:26:34]

I don't really care what it defaults to, but I do think we should lookup $SHELL,
I would assume that bash is used if SHELL is set to it

[kustermann, 2013/05/21 07:50:00]

The issue here is that different shells might interpret their arguments
differently (zsh, bash, csh ..).
As soon as we do '-c' we assume that the shell supports it. In addition to that,
we assume that all shells interpret the arguments the same way (e.g. is "ls
**/*dart" supported?).
IMHO the safest way to do it is "/bin/sh -c"

[Anders Johnsen, 2013/05/22 07:45:51]

Done.

+  }
+
+  static List<String> _getShellArguments(String executable,
+                                         List<String> arguments) {
+    List<String> shellArguments = [];
+    if (Platform.operatingSystem == 'windows') {
+      shellArguments.add("/k");
+    } else {
+      shellArguments.add("-c");
+    }
+    var commandLine = executable;
+    for (var arg in arguments) {
+      arg = arg.replaceAll("'", "'\"'\"'");

[Lasse Reichstein Nielsen, 2013/05/21 07:31:51]

You could use a multiline string here:
  """'"'"'"""
Not confusing at all :)

[Anders Johnsen, 2013/05/22 07:45:51]

Hehe, I prefer not ;)

+      commandLine = "$commandLine '$arg'";

[Lasse Reichstein Nielsen, 2013/05/21 07:13:42]

Quadratic time string concatenation. Use a StringBuffer.

[Anders Johnsen, 2013/05/22 07:45:51]

Done.

+    }
+    shellArguments.add(commandLine);
+    return shellArguments;
+  }
+
   /**
    * Returns the standard output stream of the process as a [:Stream:].
    *