Dart: Removes name conflicts from generated bindings.

examples/dart/console_example/main.dart

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 import 'dart:async';
 import 'mojo:application';
 import 'mojo:bindings';
 import 'mojo:core';
 
 import 'package:mojo/services/console/public/interfaces/console.mojom.dart';
 
 class ConsoleApplication extends Application {
-  ConsoleProxy _proxy;
+  ConsoleProxy _consoleProxy;
+  Console _console;

[sky, 2015/02/26 18:21:15]

I think this pattern (making both the proxy and interface as members) is error
prone. I lean toward using proxy.interface.foo every where. Less error prone
(but more code).

[zra, 2015/02/26 19:33:58]

I agree, just not sure how annoying it will be to type proxy.interface.call()
everywhere. I've gone ahead and removed the tear-off from all the tests and
examples. I guess if folks find it annoying, then they're welcome to tear-off on
their own.

 
   ConsoleApplication.fromHandle(MojoHandle handle) : super.fromHandle(handle);
 
   void initialize(List<String> args, String url) {
-    _proxy = new ConsoleProxy.unbound();
-    connectToService("mojo:console", _proxy);
+    _consoleProxy = new ConsoleProxy.unbound();
+    _console = _consoleProxy.interface;
+    connectToService("mojo:console", _consoleProxy);
     run();
   }
 
   run() async {
-    var result = await _proxy.readLine();
-    await _proxy.printLines([result.line]);
+    var result = await _console.readLine();
+    await _console.printLines([result.line]);
 
-    _proxy.close();
+    _consoleProxy.impl.close();
     close();
   }
 }
 
 main(List args) {
   var appHandle = new MojoHandle(args[0]);
-  var consoleApplication = new ConsoleApplication.fromHandle(appHandle);
-  consoleApplication.listen();
+  new ConsoleApplication.fromHandle(appHandle);
 }