horrible syntax error fix.
authorAndrew Sutherland <asutherland@asutherland.org>
Mon, 22 Sep 2008 17:01:17 -0700
changeset 946 23ca8d6609ae15a5b5ce8fc4a6e2cf267f1f10f5
parent 945 65e60597a8f478b9de98af81d41eba4bfdb64d43
child 947 f00184db17deab700cdd65cc01ba7f6c28d92767
push idunknown
push userunknown
push dateunknown
horrible syntax error fix.
modules/collection.js
--- a/modules/collection.js
+++ b/modules/collection.js
@@ -56,18 +56,18 @@ const LOG = Log4Moz.Service.getLogger("g
  *   query, or when their existing objects no longer match due to changes.
  * - Caching/object-identity maintenance.  It is ideal if we only ever have
  *   one instance of an object at a time.  (More specifically, only one instance
  *   per database row 'id'.)  The collection mechanism lets us find existing
  *   instances to this end.  Caching can be directly integrated by being treated
  *   as a special collection.
  */
 var GlodaCollectionManager = {
-  _collectionsByNoun = {},
-  _cachesByNoun = {},
+  _collectionsByNoun: {},
+  _cachesByNoun: {},
 
   /**
    * Registers the existence of a collection with the collection manager.  This
    *  is done using a weak reference so that the collection can go away if it
    *  wants to.
    */
   registerCollection: function gloda_colm_registerCollection(aCollection) {
     let collections;