[PPAPI] Updated documentation for PP_VarType enum constants.

ppapi/api/pp_var.idl

 /* Copyright (c) 2012 The Chromium Authors. All rights reserved.
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file.
  */
 
 /**
  * This file defines the API for handling the passing of data types between
  * your module and the page.
  */
 
@@ skipping 26 matching lines @@
 
   /**
    * A double-precision floating point value. Use the <code>as_double</code>
    * member of the var.
    */
   PP_VARTYPE_DOUBLE = 4,
 
   /**
    * The Var represents a string. The <code>as_id</code> field is used to
    * identify the string, which may be created and retrieved from the
-   * <code>PPB_Var</code> interface.
+   * <code>PPB_Var</code> interface. These objects are reference counted, so

[yzshen1, 2013/09/03 18:04:54]

If you would like to mention about ref counting, all types below, not just
string/array/dictionary should have the same comment.

[Matt Giuca, 2013/09/04 00:12:53]

Done. The reason I did that was because the existing ARRAY and DICTIONARY
documentation mentioned it. Do you actually want all of these to have the same
text?

[yzshen1, 2013/09/04 00:18:15]

Yes, mentioning it for string/array/dictionary but not object/array_buffer
sounds like the latter two don't require ref counting.

You could talk about ref counting above "enum PP_VarType". That way you don't
need to repeat the text 5 times.

BTW, I cannot see your latest patch.

+   * AddRef and Release must be used properly to avoid memory leaks.
    */
   PP_VARTYPE_STRING = 5,
 
   /**
    * Represents a JavaScript object. This vartype is not currently usable
    * from modules, although it is used internally for some tasks.
    */
   PP_VARTYPE_OBJECT = 6,
 
   /**
-   * Arrays and dictionaries are not currently supported but will be added
-   * in future revisions. These objects are reference counted so be sure
-   * to properly AddRef/Release them as you would with strings to ensure your
-   * module will continue to work with future versions of the API.
+   * Represents an array of Vars. The <code>as_id</code> field is used to
+   * identify the array, which may be created and manipulated from the
+   * <code>PPB_VarArray</code> interface. These objects are reference counted,
+   * so AddRef and Release must be used properly to avoid memory leaks.
    */
   PP_VARTYPE_ARRAY = 7,
+
+  /**
+   * Represents a mapping from strings to Vars. The <code>as_id</code> field is
+   * used to identify the dictionary, which may be created and manipulated from
+   * the <code>PPB_VarDictionary</code> interface. These objects are reference
+   * counted, so AddRef and Release must be used properly to avoid memory leaks.
+   */
   PP_VARTYPE_DICTIONARY = 8,
 
   /**
    * ArrayBuffer represents a JavaScript ArrayBuffer. This is the type which
    * represents Typed Arrays in JavaScript. Unlike JavaScript 'Array', it is
    * only meant to contain basic numeric types, and is always stored
    * contiguously. See PPB_VarArrayBuffer_Dev for functions special to
    * ArrayBuffer vars.
    */
   PP_VARTYPE_ARRAY_BUFFER = 9
@@ skipping 142 matching lines @@
   struct PP_Var result = { PP_VARTYPE_DOUBLE, 0, {PP_FALSE} };
   result.value.as_double = value;
   return result;
 }
 /**
  * @}
  */
 
 #endinl