frog: life is better with colors :)

frog/minfrog.dart

Index: frog/minfrog.dart
diff --git a/frog/minfrog.dart b/frog/minfrog.dart
index 575900985bb16084dc3797dfa21e9e70b1035ca7..51c0398e1135c9d5f01ecb2b9cf2e54a5afe9cd6 100644
--- a/frog/minfrog.dart
+++ b/frog/minfrog.dart
@@ -18,6 +18,11 @@ void main() {
   var argv = new List.from(process.argv);
 
   if (compile(homedir, argv, new NodeFileSystem())) {
+    if (options.outfile !== null) {

[Jennifer Messerly, 2011/12/06 22:50:03]

I won't add this message unless doing "compileOnly"

if you're just running a Dart script, it's important not to output extra stuff.
Imagine if every Python script printed "compilation succeeded" before running :)

so something like:
if (options.compileOnly) {
  // print compilation succeeded message
} else {
  var code = world.getGeneratedCode();
  process.argv = [argv[0], argv[1]];
  // ... vm.runInNewContext ...
}

[Siggi Cherem (dart-lang), 2011/12/06 23:37:38]

The other opinion I heard earlier today was that people wanted to see clearly
when did compilation finished and we started running the actual script (so it is
clear why something failed).

I followed your suggestion for now. Another option is to print this message in 2
scenarios:
- compile only
- compile + run, but outfile was specified.

+      print('Compilation succeded. Code generated in ${options.outfile}');
+    } else {
+      print('Compilation succeded.');
+    }
     var code = world.getGeneratedCode();
     if (!options.compileOnly) {
       process.argv = [argv[0], argv[1]];