dart-sdk/tests/language_2/class_syntax_test.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.

main() {
  new ClassSyntaxTest();
}

class ClassSyntaxTest {
  /* //# 01: syntax error
}
*/ //# 01: continued
Report parser error if a class isn't terminated by }. Review URL: https://codereview.chromium.org//11348216 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@15383 260f80e4-7a28-3924-810f-c04153c831b5 2012-11-27 11:47:59 +00:00			`// 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.`

			`main() {`
			`new ClassSyntaxTest();`
			`}`

			`class ClassSyntaxTest {`
Adds support for `syntax error` in tests to test.py. This CL modifies the Dart source used from test.py such that it takes `syntax error` into account as an expected outcome in test files (so that we can have `//# 01: syntax error` with a similar meaning as `//# 01: compile-time error`). For all tools except the spec_parser, `syntax error` is the same outcome as `compile-time error`; that is, nobody else will see the difference. For the spec_parser, `syntax error` is the outcome where parsing has failed; `compile-time error` is taken to mean some other compile-time error, i.e., the spec_parser is expected to _succeed_ when the expected outcome is `compile-time error`. Test files in language and language_2 have been adjusted to use the outcome `syntax error` where appropriate. The status files in language and language_2 for the spec_parser have been adjusted such that they fit all the new `syntax error` outcomes in test files. Other status files have been adjusted in a few cases where tests were corrected (because a compile-time error which was clearly not intended to be a syntax error turned out to be caused by a typo, which means that the actual compile-time error has never been tested). The spec grammar Dart.g was adjusted in a few cases, when some bugs were discovered. In particular, the treatment of Function has been changed: It is now known by the parser that Function does not take any type arguments. This makes no difference for developers, because they cannot declare a type named Function anyway, but it means that a number of tricky parsing issues were resolved. Dart.g was also adjusted to allow `qualified` to contain three identifiers, which is an old bug (preventing things like metadata on the form `@p.C.myConst`). Change-Id: Ie420887d45c882ef97c84143365219f8aa0d2933 Reviewed-on: https://dart-review.googlesource.com/18262 Commit-Queue: Erik Ernst <eernst@google.com> Reviewed-by: Bob Nystrom <rnystrom@google.com> Reviewed-by: Lasse R.H. Nielsen <lrn@google.com> 2017-11-06 08:56:09 +00:00			`/* //# 01: syntax error`
Report parser error if a class isn't terminated by }. Review URL: https://codereview.chromium.org//11348216 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@15383 260f80e4-7a28-3924-810f-c04153c831b5 2012-11-27 11:47:59 +00:00			`}`
Fix warnings_checker.dart handling of multitests Update all tests Support //# multitests for better dartfmt compatibility and fewer multitest false positives All files under tests were manually updated with find . -iregex '.*\.dart$' -print0 \| xargs -0 perl -pi -e 's/(\S\s+)\/\/\/ /$1\/\/# /' For now both old and new styles are allowed to accommodate CO19 tests. R=efortuna@google.com BUG= Review-Url: https://codereview.chromium.org/2765693002 . Review-Url: https://codereview.chromium.org/2765893003 . 2017-03-22 00:29:56 +00:00			`*/ //# 01: continued`