Migrated cascades tests from dart2js_extra into language tests

Migrated cascades tests from dart2js_extra into language tests

See issues for VM and Analyzer implementation:
  http://code.google.com/p/dart/issues/detail?id=2150
  http://code.google.com/p/dart/issues/detail?id=3729

Committed: https://code.google.com/p/dart/source/detail?r=8845

[zundel, 2012-06-19 11:59:16]

I think these two tests are of general utility for all implementations.

[kasperl, 2012-06-19 13:47:15]

LGTM! Thanks, Eric.

https://chromiumcodereview.appspot.com/10559064/diff/2001/tests/language/lang...
File tests/language/language.status (right):

https://chromiumcodereview.appspot.com/10559064/diff/2001/tests/language/lang...
tests/language/language.status:56: cascade_test: Pass,Fail  # Some cases pass,
but for the wrong reason
You could also split them out into the different /01 variants, but I guess this
is easier for now -- and still allows you to start making progress.

[zundel, 2012-06-19 13:54:30]

https://chromiumcodereview.appspot.com/10559064/diff/2001/tests/language/lang...
File tests/language/language.status (right):

https://chromiumcodereview.appspot.com/10559064/diff/2001/tests/language/lang...
tests/language/language.status:56: cascade_test: Pass,Fail  # Some cases pass,
but for the wrong reason
On 2012/06/19 13:47:15, kasperl wrote:
> You could also split them out into the different /01 variants, but I guess
this
> is easier for now -- and still allows you to start making progress.

Enumerating them out isn't any more helpful IMHO.  The feature is unimplemented.
The tests that 'pass' do so because a compile time error is expected but really
its a syntax error on not being able to parse the cascade syntax.