478803 - Regex.test with -ES3 returns incorrect value

Status: VERIFIED INVALID

(Tamarin Graveyard :: Virtual Machine, defect, P4)

Description

[Jeff Dyer]

This is somewhat obscure...
code:
var x = new RegExp(null);
trace(x.test(undefined));

Compile with -ES3 on OS X

Actual Results: false

Expected Results: true

This evaluates to true for all other cases of using null and undefined:
var x = new RegExp(undefined);
trace(x.test(undefined)); //true

var x = new RegExp(null);
trace(x.test(null)); //true

var x = new RegExp(undefined);
trace(x.test(null));  //true

        
        
Transferred Comments:

BugDB Migration - Mon Jun 04 12:32:46 CDT 2007
[cpeyer 12/14/06] Entered Bug.

JIRA Migration Admin - Mon Jun 04 12:32:46 CDT 2007
Milestone ID = 1378
Milestone = FP 10 - Code Complete
Build ID = 23495
Build = AVMPLUS_1_0_0_d693
Fix Build ID = null
Fix Build = null


JIRA Migration Admin - Mon Jun 04 12:32:46 CDT 2007
Move from BugDB issue number 193487

Trevor Baker - Tue Jan 27 16:03:53 CST 2009
back to internal review for reprioritization


This bug transferred from: http://bugs.adobe.com/jira/browse/ASC-2259

Comment 1

[Michael Daumling]

This is expected behavior. See ECMA-262 15.10.4.1: new RegExp(undefined) == // (the empty string), and new RegExp(null) == /null/.

The empty string matches "undefined", but /null/ does not match "undefined".