aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDomenic Denicola2013-06-24 15:34:54 -0300
committerPete Bacon Darwin2013-06-25 21:13:32 +0100
commit00d890c07abe538fb414b7eba496f924c3526fe0 (patch)
tree6035eed380e08a4d005fc69289243f2c5cdaf938
parentaef098006302689d2d75673be828e31903ee7c3c (diff)
downloadangular.js-00d890c07abe538fb414b7eba496f924c3526fe0.tar.bz2
docs(guide/expression): remove reference to `NullPointerException`
-rw-r--r--docs/content/guide/expression.ngdoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/content/guide/expression.ngdoc b/docs/content/guide/expression.ngdoc
index 62b5f8d8..eae41fcf 100644
--- a/docs/content/guide/expression.ngdoc
+++ b/docs/content/guide/expression.ngdoc
@@ -23,8 +23,8 @@ You can think of Angular expressions as JavaScript expressions with following di
evaluation, unlike in JavaScript where the expressions are evaluated against the global
`window`.
- * **Forgiving:** expression evaluation is forgiving to undefined and null, unlike in JavaScript,
- where such evaluations generate `NullPointerExceptions`.
+ * **Forgiving:** expression evaluation is forgiving to `undefined` and `null`, unlike in JavaScript,
+ where trying to evaluate undefined properties can generate `ReferenceError` or `TypeError`.
* **No Control Flow Statements:** you cannot do any of the following in angular expression:
conditionals, loops, or throw.