Add regex support in policy schema

components/policy/core/common/schema_internal.h

Index: components/policy/core/common/schema_internal.h
diff --git a/components/policy/core/common/schema_internal.h b/components/policy/core/common/schema_internal.h
index 86e6a2b75b20f16e6d2e98c3840a5df9ad353c26..f1613e15096736e5359739b42d83764490c7f130 100644
--- a/components/policy/core/common/schema_internal.h
+++ b/components/policy/core/common/schema_internal.h
@@ -63,6 +63,13 @@ struct POLICY_EXPORT PropertiesNode {
   // properties can be looked up by binary searching in the range.
   int end;
 
+  // An offset into SchemaData::property_nodes that indexes the PropertyNode
+  // right byond the last known pattern property.

[Joao da Silva, 2014/03/21 12:58:12]

beyond

[binjin, 2014/03/27 17:57:47]

Done.

+  //
+  // [end, pattern_end) is the range that covers all pattern properties
+  // defined. It's not required to be sorted.
+  int pattern_end;
+
   // If this map policy supports keys with any value (besides the well-known
   // values described in the range [begin, end)) then |additional| is an offset
   // into SchemaData::schema_nodes that indexes the SchemaNode describing the
@@ -92,6 +99,14 @@ union POLICY_EXPORT RestrictionNode {
     int max_value;
     int min_value;
   } ranged_restriction;
+
+  // For string type only, require |pattern_index| and |pattern_index_backup|

[Joao da Silva, 2014/03/21 12:58:12]

requires

[binjin, 2014/03/27 17:57:47]

Done.

+  // to be exactly same. And it's an offset into SchemaData::string_enums

[Joao da Silva, 2014/03/21 12:58:12]

to be exactly the same

[binjin, 2014/03/27 17:57:47]

Done.

+  // which contains the regular expression that the target string must follow.
+  struct StringPatternRestriction {
+    int pattern_index;
+    int pattern_index_backup;
+  } string_pattern_restriction;
 };