Paul Berry
cf1d8b96db
Changes the signature of the following constructors: - Scanner - Scanner.fasta - Parser So that they accept a `DiagnosticReporter` object rather than a `DiagnosticListener` object. This brings the scanner and the parser into alignment with the majority of the rest of the analyzer (which reports errors using `DiagnosticReporter` rather than by talking to `DiagnosticListener` directly). It also makes the `source` parameter of these constructors unnecessary, because the `source` can be obtained from the `DiagnosticReporter`. Change-Id: I6a6a6964607ffb52a8332a6e618dc0c9a1e48c5c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/473442 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Bob Nystrom <rnystrom@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Paul Berry <paulberry@google.com>
SDK development code analysis
dartanalyzer used to be the tool for statically analyzing dart code
at the command line. However, this tool has been replaced with
dart analyze for this purpose in current SDKs and will no longer
be published on pub.
Do not depend on the command line interface or other semantics in
this directory as it is now an internal tool for SDK development, used
as the dart2analyzer "compiler" for tools/test.py in the SDK.
It is configured as part of the test runner,
here.
SDK development usage
For SDK development, run analysis from the test tool to validate analysis conclusions on language samples in the testing directory. From the root of the SDK:
tools/test.py --build --use-sdk -c dart2analyzer co19 language
This will build the Dart VM and compile dartanalyzer into a snapshot, then use
that snapshot while analyzing those directories under testing/. Without
--use-sdk, test.py will use the source code version of the analyzer
instead of the compiled one, which can be useful for debugging.