Added JSON schema compiler support for serialized types

tools/json_schema_compiler/cpp_util.py

 # 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.
 """Utilies and constants specific to Chromium C++ code.
 """
 
 from datetime import datetime
 from model import PropertyType
 import os
 
@@ skipping 56 matching lines @@
       PropertyType.STRING):
     arg = '%(type)s& %(name)s'
   else:
     arg = '%(type)s %(name)s'
   return arg % {
     'type': type_,
     'name': param.unix_name,
   }
 
 def GenerateIfndefName(path, filename):
-    """Formats a path and filename as a #define name.
+  """Formats a path and filename as a #define name.
 
-    e.g chrome/extensions/gen, file.h becomes CHROME_EXTENSIONS_GEN_FILE_H__.
-    """
-    return (('%s_%s_H__' % (path, filename))
-            .upper().replace(os.sep, '_').replace('/', '_'))
+  e.g chrome/extensions/gen, file.h becomes CHROME_EXTENSIONS_GEN_FILE_H__.
+  """
+  return (('%s_%s_H__' % (path, filename))
+          .upper().replace(os.sep, '_').replace('/', '_'))
+
+def DoConversion(prop, from_, to):
+  """Converts from prop.type_ to prop.serialized_type.

[not at google - send to devlin, 2012/07/26 04:51:42]

erm maybe a less ambiguous name, like GenerateTypeConversionCall or something.

Please also describe what from_ and to are.

[mitchellwrosen, 2012/07/26 20:00:27]

Done.

+  """
+  # TODO(mwrosen): Add support for more from/to combinations as necessary.
+  return {
+      PropertyType.STRING: {
+          PropertyType.INTEGER: 'base::StringToInt(%s, %s)',
+          PropertyType.INT64: 'base::StringToInt64(%s, %s)'
+      }[prop.serialized_type] % (from_, to)
+  }[prop.type_]

[not at google - send to devlin, 2012/07/26 04:51:42]

here and above, what happens if the types aren't supported? I think it would
return None thing or something. But it should raise an exception.

[mitchellwrosen, 2012/07/26 20:00:27]

It'll return a KeyError. Should I catch that and raise something else?

[not at google - send to devlin, 2012/07/27 04:14:28]

Yeah, would be nice to include in the exception why it's happening (so that the
poor hapless future user of this doesn't have to dig through python source code
to figure out what the problem is).

And NotImplementedError would be more appropriate.

[mitchellwrosen, 2012/07/30 20:52:45]

Done.