Remove printDebugInfo from Unparser

lib/compiler/implementation/tree/unparser.dart

Index: lib/compiler/implementation/tree/unparser.dart
diff --git a/lib/compiler/implementation/tree/unparser.dart b/lib/compiler/implementation/tree/unparser.dart
index fa19630a860ee9e590921410978c94d96d0c65a7..9f9b5b591b3971ca7bc7e95c73b8df61cd65635a 100644
--- a/lib/compiler/implementation/tree/unparser.dart
+++ b/lib/compiler/implementation/tree/unparser.dart
@@ -4,9 +4,8 @@
 
 class Unparser implements Visitor {
   StringBuffer sb;
-  final bool printDebugInfo;
 
-  Unparser([this.printDebugInfo = false]);
+  Unparser();
 
   String unparse(Node node) {
     sb = new StringBuffer();
@@ -20,11 +19,7 @@ class Unparser implements Visitor {
 
   visit(Node node) {
     if (node !== null) {

[Anton Muhin, 2012/06/05 09:35:19]

probably it's time to go single line now: if (node !== null) node.accept(this);

[Roman, 2012/06/05 11:09:07]

Done.

By the way, Dart style guide is ambiguous:
http://www.dartlang.org/articles/style-guide/

On one hand, it says: "DO use curly braces for all flow control structures.",
but later there is "green example":
if (obj is! SomeType) print('not SomeType');

[Anton Muhin, 2012/06/05 11:39:21]

You may want to file a bug.

Historically, at least AAR people use single line variants a lot.

On 2012/06/05 11:09:07, Roman wrote:

-      if (printDebugInfo) sb.add('[${node.getObjectDescription()}: ');
       node.accept(this);
-      if (printDebugInfo) sb.add(']');
-    } else if (printDebugInfo) {
-      sb.add('[null]');
     }
   }