From 0b62c92cb3dc0eca333b1d94b285af0bdd4fc24c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89ric=20Lemoine?= <eric.lemoine@gmail.com>
Date: Tue, 26 Mar 2013 17:05:54 +0100
Subject: [PATCH] Use @expose for Coordinate.z

By annotating the z property with @expose the compiler does not try to optimize that property in any way. See https://developers.google.com/closure/compiler/docs/js-for-compiler. The doc says that @expose should never be used in library code, but that's the only way I found for our case.
---
 src/ol/coordinate.js | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/ol/coordinate.js b/src/ol/coordinate.js
index ba94382d95..189b59b8fa 100644
--- a/src/ol/coordinate.js
+++ b/src/ol/coordinate.js
@@ -26,6 +26,7 @@ ol.Coordinate = function(x, y, opt_z) {
   goog.base(this, x, y);
 
   /**
+   * @expose
    * @type {number}
    */
   this.z = goog.isDef(opt_z) ? opt_z : NaN;