refactoring for pdf viewer lib

experimental/PdfViewer/autogen/SkPdfStandardStructureDictionary_autogen.h

 #ifndef __DEFINED__SkPdfStandardStructureDictionary
 #define __DEFINED__SkPdfStandardStructureDictionary
 
 #include "SkPdfUtils.h"
 #include "SkPdfEnums_autogen.h"
 #include "SkPdfArray_autogen.h"
 #include "SkPdfDictionary_autogen.h"
 
 // Standard layout attributes common to all standard structure types
 class SkPdfStandardStructureDictionary : public SkPdfDictionary {
@@ skipping 551 matching lines @@
  *  reference area, or placed serially against the edge, in the order encountered.
  *       Complex cases such as floating elements that interfere with each other or do not
  *       fit on the same page may be handled differently by different layout applications;
  *       Tagged PDF merely identifies the elements as floating and indicates their desired
  *       placement.
 **/
   bool has_Placement() const {
     return (ObjectFromDictionary(fPodofoDoc, fPodofoObj->GetDictionary(), "Placement", "", NULL));
   }
 
-  std::string Placement() const {
-    std::string ret;
-    if (NameFromDictionary(fPodofoDoc, fPodofoObj->GetDictionary(), "Placement", "", &ret)) return ret;
-    // TODO(edisonn): warn about missing required field, assert for known good pdfs
-    return "";
-  }
-
+  std::string Placement() const;
 /** (Optional) The directions of layout progression for packing of ILSEs (inline
  *  progression) and stacking of BLSEs (block progression):
  *      LrTb         Inline progression from left to right; block progression from
  *                   top to bottom. This is the typical writing mode for Western
  *                   writing systems.
  *      RlTb         Inline progression from right to left; block progression from
  *                   top to bottom. This is the typical writing mode for Arabic
  *                   and Hebrew writing systems.
  *      TbRl         Inline progression from top to bottom; block progression
  *                   from right to left. This is the typical writing mode for Chi-
  *                   nese and Japanese writing systems.
  *  The specified layout directions apply to the given structure element and all of
  *  its descendants to any level of nesting. Default value: LrTb.
  *  For elements that produce multiple columns, the writing mode defines the
  *  direction of column progression within the reference area: the inline direc-
  *  tion determines the stacking direction for columns and the default flow
  *  order of text from column to column. For tables, the writing mode controls
  *  the layout of rows and columns: table rows (structure type TR) are stacked
  *  in the block direction, cells within a row (structure type TD) in the inline
  *  direction.
  *  Note: The inline-progression direction specified by the writing mode is subject to
  *  local override within the text being laid out, as described in Unicode Standard
  *  Annex #9, The Bidirectional Algorithm, available from the Unicode Consor-
  *  tium (see the Bibliography).
 **/
   bool has_WritingMode() const {
     return (ObjectFromDictionary(fPodofoDoc, fPodofoObj->GetDictionary(), "WritingMode", "", NULL));
   }
 
-  std::string WritingMode() const {
-    std::string ret;
-    if (NameFromDictionary(fPodofoDoc, fPodofoObj->GetDictionary(), "WritingMode", "", &ret)) return ret;
-    // TODO(edisonn): warn about missing required field, assert for known good pdfs
-    return "";
-  }
-
+  std::string WritingMode() const;
 };
 
 #endif  // __DEFINED__SkPdfStandardStructureDictionary