error handling - Catching "NullPointerExceptions" in JavaScript - Stack Overflow

admin管理员组

文章数量:1291597

I'm writing quite a bit of code in Prototype.js which returns null if a DOM-id wasn't found.

$("someId").show();

If someId doesn't exist, a method will be called on null, which halts the entire program, in effect disabling all JS effects after the error. I could just check for null before executing such a statement, but this is getting tiring.

I would like to catch an exception but I'm not sure which one its is. MDC lists the following ECMA Script error types, but on first glance none of them seem to be what I want:

* Error
* EvalError
* RangeError
* ReferenceError
* SyntaxError
* TypeError
* URIError
* DOMException
* EventException
* RangeException

Also, do browsers have a unified way of dealing with a method call on null?

I'm writing quite a bit of code in Prototype.js which returns null if a DOM-id wasn't found.

$("someId").show();

If someId doesn't exist, a method will be called on null, which halts the entire program, in effect disabling all JS effects after the error. I could just check for null before executing such a statement, but this is getting tiring.

I would like to catch an exception but I'm not sure which one its is. MDC lists the following ECMA Script error types, but on first glance none of them seem to be what I want:

* Error
* EvalError
* RangeError
* ReferenceError
* SyntaxError
* TypeError
* URIError
* DOMException
* EventException
* RangeException

Also, do browsers have a unified way of dealing with a method call on null?

• javascript
• error-handling

Share Follow asked Apr 27, 2010 at 12:31 Leonard EhrenfriedLeonard Ehrenfried 1,61333 gold badges2222 silver badges3434 bronze badges 2

• 5 I could just check for null before executing such a statement, but this is getting tiring. Huh? Are you a developer or not? Writing robust code with checks is a normal and good practice. – BalusC Commented Apr 27, 2010 at 12:40
• Good point, but repeatedly nested if clauses make my code really unreadable. I should have said that instead of 'tiring'. – Leonard Ehrenfried Commented Apr 27, 2010 at 12:54

Add a ment  | 

4 Answers 4

Sorted by: Reset to default 2

I don't believe there's unity to be found. Chrome throws a TypeError, but IE throws an Error, so you would probably have to catch everything and make severe assumptions. Better to check for null first.

var element = $('someId');
if (element) {
    element.show();
    // whatever else...
}

If element.show() is the only thing you need it for, then it can obviously be written a lot shorter, but in most cases that would be appropriate.

The correct way to handle this is to check for null before doing something with an object. There are several shorthand ways to do this, the shortest is (as Alex K) wrote

$("someId") && $("someId").show();

but this seems to me to be harder to read.

To answer your question directly you can do

try { $('someId').show(); } catch (e) {} 

but this seems amateurish. You should program explicitly because later on someone else won't know why you wrote that odd code. The first example is slightly opaque but at least contains the null test first, and doesn't hide errors in the show() method.

Incidentally, if you were using JQuery instead of Prototype, this code would work without error even if there is no object with id 'someId':

$('#someId').show()

That's because the $() function in JQuery returns a collection which may be empty but is never null.

If your going to chain .show() on $("someId") then check its result first.

if ($("someId"))
   $("someId").show();

or

$("someId") && $("someId").show();

or

if (someVar = $("someId"))
   someVar.show();

If for some reason you really need to identify them you could wrap $() and throw a custom exception:

function NullReferenceException(id) {this.id = id}

function $my(id) {
    var el = $(id);
    if (!el)
        throw new NullReferenceException(id);
    return el
}

try {
    $my("iDontExistId").show();
} catch (e) {
    if (e instanceof NullReferenceException)
        alert(e.id + " doesn't exist");
}

Just ignore which exception it is...

try
{
    null.hey()
}
catch(e)
{
    //handle it here
}

本文标签： error handlingCatching quotNullPointerExceptionsquot in JavaScriptStack Overflow