Reviewers: dcarney,

Message:
Committed patchset #1 manually as r18036.

Description:
Experimental parser: Test file fix.

It helps to run with the correct lexer-shell flag (--utf8).

[email protected]
BUG=

Committed: https://code.google.com/p/v8/source/detail?r=18036

Please review this at https://codereview.chromium.org/85333002/

SVN Base: https://v8.googlecode.com/svn/branches/experimental/parser

Affected files (+8, -11 lines):
  M test/lexer/cornercases/utf-endlines.js


Index: test/lexer/cornercases/utf-endlines.js
diff --git a/test/lexer/cornercases/utf-endlines.js b/test/lexer/cornercases/utf-endlines.js index 8ac1ee2fa895d691403ed0f6865a7dfd312b9a8c..d5987db6cddca3f92449732d4153fd86252b73af 100644
--- a/test/lexer/cornercases/utf-endlines.js
+++ b/test/lexer/cornercases/utf-endlines.js
@@ -30,6 +30,7 @@

// This file tests if it's recognized after various Unicode new line markers:

+// Recognized as a newline (the break keyword not seen).
 "Line feed":
 --> break

@@ -39,17 +40,19 @@
 // Form feed is not recognized as a newline.
 "Form feed":--> catch

+// Recognized as a newline.
 "Carriage return":
--> const

+// Recognized as a newline.
 "Carriage return and line feed:"
 --> continue

-// Next line is not regonized as a newline, instead it's recognized as an identifier.
+// Recognized as a newline.
 "Next line":…
 --> debugger

-// Line separator is not recognized as a newline, instead it's ILLEGAL.
-//"Line separator":
--> default
+// Recognized as a newline.
+"Line separator":
--> default

-// Paragraph separator is not recognized as a newline, instead it's ILLEGAL.
-//"Paragraph separator":
--> delete
\ No newline at end of file
+// Recognized as a newline.
+"Paragraph separator":
--> delete
\ No newline at end of file


--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to