Closed Bug 485299 Opened 15 years ago Closed 12 years ago

Difference in lambda functions, uneval() and toString()

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: BijuMailList, Unassigned)

Details

(Keywords: testcase) 

Difference in lambda function uneval() and toString()



function x(i)i*i*i;
uneval(x);
===>
function x(i) i * i * i;


x=(function x()i*i*i);
uneval(x);
===>
(function x() i * i * i)




function x(i)i*i*i;
x.toSource();
===>
function x(i) i * i * i;


x=(function x()i*i*i);
x.toSource();
===>
(function x() i * i * i)





function x(i)i*i*i;
x.toString();
===>
function x(i) i * i * i;



x=(function x()i*i*i);
x.toString();
===>
function x() i * i * i



Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre)
Gecko/20090324 Minefield/3.6a1pre

my pref
javascript.options.jit.content=true
javascript.options.jit.chrome=false
Keywords: testcase
Fixed by saving the source.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.