qunit throws syntax error on Safari 2.0.4

[micmath]

It is not possible to use qunit to run tests in the Safari 2.0.4 browser, which is still a Level 2 browser here at the BBC. This is because qunit uses a function declaration pattern that Safari 2.0.4 considers to be a "syntax error."

// snip
test: function test (testName, callback) { // throws error
}

Rewriting those function declarations to be like the following example will allow qunit to run in Safari 2.0.4.

//snip
test: function (testName, callback) { // runs
}

[DBJDBJ]

I do not know why are "named function expressions" used here,but if they are needed, one can do this :

var temp;
...
var Qunit = {
test: (temp = function test(){ ... }) ;
...
}
...
temp = null;

This is actually quite good for avoiding lekas too ...
--DBJ

[DBJDBJ]

lekas --> leaks

[jeresig]

Remove the named function expressions, to stop Safari 2 from freaking out. Closed by f55bf2d.

[DBJDBJ]

Good. The only reason I can remember, to use named F expressions, is to be able to "see" named (vs anonymous) functions in (visual studio) debugger ...
--DBJ

[micmath]

This issue, and a possible solution for Safari 2, is discussed further here, in case anyone is interested: http://yura.thinkweb2.com/named-function-expressions/#named-expr

[DBJDBJ]

I do not think jQuery or (BBC) Glow will ever have "named function expressions" inside ... Sorry for the noise ;o)