Dartdoc and Apidoc updated to use dart2js through the mirror system.

lib/compiler/implementation/apiimpl.dart

 // Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 #library('leg_apiimpl');
 
 #import('dart:uri');
 
 #import('../compiler.dart', prefix: 'api');
 #import('leg.dart', prefix: 'leg');
@@ skipping 87 matching lines @@
       log('${task.name} took ${task.timing}msec');
     }
     return success;
   }
 
   void reportDiagnostic(leg.SourceSpan span, String message,
                         api.Diagnostic kind) {
     if (kind === api.Diagnostic.ERROR || kind === api.Diagnostic.CRASH) {
       compilationFailed = true;
     }
-    if (span === null) {
+    // [:span.uri:] might be [:null:] in case of a [Script] with no [uri]. For
+    // instance in the [Types] constructor in typechecker.dart.

[Bob Nystrom, 2012/07/09 16:59:55]

I find myself doing this too out of habit, but, for what it's worth, there's
little point in using dartdoc formatting in non-doc comments like this. They'll
never be processed. I suppose if we ever make a literate programming version of
dartdoc that does process in-source comments, maybe this would be useful...

[Johnni Winther, 2012/07/12 08:51:39]

The [:...:] syntax doesn't look good, but the [...] actually makes comments more
readable since they easily mark when a word a code entity.

[Bob Nystrom, 2012/07/12 16:42:30]

True on []. Also, since dartdoc is markdown, you can also use backticks instead
of [:...:].

+    if (span === null || span.uri === null) {
       handler(null, null, null, message, kind);
     } else {
       handler(translateUri(span.uri, null), span.begin, span.end,
               message, kind);
     }
   }
 
   bool get isMockCompilation() {
     return mockableLibraryUsed
       && (options.indexOf('--allow-mock-compilation') !== -1);
   }
 }