Updates:
Cc: a...@chromium.org erikco...@chromium.org
Labels: -Area-Irregexp
Comment #1 on issue 3870 by a...@chromium.org: RegExp.multiline (global)
accessor should probably be deleted (or properly implemented)
https://code.google.com/p/v8/issues/detail?id=3870
I vote for
Comment #4 on issue 3870 by caitpott...@gmail.com: RegExp.multiline
(global) accessor should probably be deleted (or properly implemented)
https://code.google.com/p/v8/issues/detail?id=3870
Er, the implementation in V8 is compatible with JSC* =)
--
You received this message because this
Comment #5 on issue 3870 by a...@chromium.org: RegExp.multiline (global)
accessor should probably be deleted (or properly implemented)
https://code.google.com/p/v8/issues/detail?id=3870
erikcorry: This bug is about removing RegExp.multiline, not the multiline
property on regexp instance
Comment #2 on issue 3870 by erikco...@google.com: RegExp.multiline (global)
accessor should probably be deleted (or properly implemented)
https://code.google.com/p/v8/issues/detail?id=3870
At the moment it is compatible with Safari:
re = /foo/m
re.multiline // true
re2 = /foo/
Comment #3 on issue 3870 by caitpott...@gmail.com: RegExp.multiline
(global) accessor should probably be deleted (or properly implemented)
https://code.google.com/p/v8/issues/detail?id=3870
This thread is about RegExp.multiline, the static accessor of the RegExp
object
Comment #6 on issue 3870 by brian.te...@gmail.com: RegExp.multiline
(global) accessor should probably be deleted (or properly implemented)
https://code.google.com/p/v8/issues/detail?id=3870
Chakra doesn't implement RegExp.multiline at all so the risk of web
breakage due to removing it
