« Bugzilla Issues Index
#3505 — Should `regexp.compile(regexp, flags)` also no longer throws just like the RexExp constructor did in rev29 for consistency?
- bug_id:
3505
- creation_ts:
2015-01-01 19:58:00 -0800
- short_desc:
Should `regexp.compile(regexp, flags)` also no longer throws just like the RexExp constructor did in rev29 for consistency?
- delta_ts:
2015-02-11 10:51:51 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 30: December 24, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
WONTFIX
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
ziyunfei
- assigned_to:
Allen Wirfs-Brock
- cc:
["dherman", "jorendorff", "samth"]
- commentid:
11291
- comment_count:
0
- who:
ziyunfei
- bug_when:
2015-01-01 19:58:31 -0800
- commentid:
12310
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-11 10:51:51 -0800
No, compile exists only as a method legacy that no body should ever use in new code.
Generalizing it to work better with RegExp subclasses is not needed and might encourage its continued use.