| /third_party/libphonenumber/javascript/i18n/phonenumbers/ |
| D | phonemetadata.pb.js | 41 goog.proto2.Message.call(this);
43 goog.inherits(i18n.phonenumbers.NumberFormat, goog.proto2.Message);
386 goog.proto2.Message.call(this);
388 goog.inherits(i18n.phonenumbers.PhoneNumberDesc, goog.proto2.Message);
640 goog.proto2.Message.call(this);
642 goog.inherits(i18n.phonenumbers.PhoneMetadata, goog.proto2.Message);
2270 goog.proto2.Message.call(this);
2272 goog.inherits(i18n.phonenumbers.PhoneMetadataCollection, goog.proto2.Message);
2365 fieldType: goog.proto2.Message.FieldType.STRING,
2371 fieldType: goog.proto2.Message.FieldType.STRING,
[all …]
|
| D | phonenumber.pb.js | 40 goog.proto2.Message.call(this);
42 goog.inherits(i18n.phonenumbers.PhoneNumber, goog.proto2.Message);
494 fieldType: goog.proto2.Message.FieldType.INT32,
500 fieldType: goog.proto2.Message.FieldType.UINT64,
505 fieldType: goog.proto2.Message.FieldType.STRING,
510 fieldType: goog.proto2.Message.FieldType.BOOL,
515 fieldType: goog.proto2.Message.FieldType.INT32,
521 fieldType: goog.proto2.Message.FieldType.STRING,
526 fieldType: goog.proto2.Message.FieldType.ENUM,
532 fieldType: goog.proto2.Message.FieldType.STRING,
[all …]
|
| /third_party/protobuf/docs/csharp/ |
| D | proto2.md | 1 …proto2 support has been released. This document outlines the new changes brought about to include …
2 Generated code for proto2 may also be modified by adding, removing, or adjusting APIs as feedback i…
4 ### Enabling proto2 features
6 For information about specific proto2 features, please read the [proto2 language guide](https://dev…
8 …proto2 features are used with proto2 files with the syntax declaration `syntax = "proto2";`. Howev…
14 Messages in proto2 files are very similar to their proto3 counterparts. They expose the usual prope…
100 Initialization refers to checking the status of required fields in a proto2 message. If a message i…
154 Reflection APIs have been extended to enable accessing the new proto2 portions of the library and g…
|
| /third_party/protobuf/python/google/protobuf/internal/ |
| D | reflection_test.py | 293 proto2 = message_module.TestAllTypes()
294 proto2.optional_nested_message.bb = 5
295 proto1.MergeFrom(proto2)
407 proto2 = message_module.TestAllTypes()
408 proto2.ParseFromString(proto.SerializeToString())
409 self.assertIsInstance(getattr(proto2, field_name), expected_type)
663 proto2 = message_module.TestAllTypes.FromString(string1)
666 self.assertEqual(proto2, proto1)
673 proto2 = message_module.TestAllTypes()
675 proto2.optional_string = 'value'
[all …]
|
| /third_party/protobuf/ruby/tests/ |
| D | test_import_proto2.proto | 1 syntax = "proto2";
3 package foo_bar.proto2;
|
| D | generated_code_proto2.proto | 1 syntax = "proto2";
3 package a.b.proto2;
|
| /third_party/protobuf/benchmarks/python/ |
| D | python_benchmark_messages.cc | 19 benchmarks::proto2::GoogleMessage1().descriptor(); in initlibbenchmark_messages()
20 benchmarks::proto2::GoogleMessage2().descriptor(); in initlibbenchmark_messages()
|
| /third_party/protobuf/src/google/protobuf/ |
| D | unittest_lazy_dependencies_enum.proto | 37 syntax = "proto2";
40 // See: http://go/proto2-generic-services-default
46 // We don't put this in a package within proto2 because we need to make sure
47 // that the generated code doesn't depend on being in the proto2 namespace.
|
| D | unittest_lazy_dependencies_custom_option.proto | 37 syntax = "proto2";
43 // See: http://go/proto2-generic-services-default
49 // We don't put this in a package within proto2 because we need to make sure
50 // that the generated code doesn't depend on being in the proto2 namespace.
|
| D | unittest_lazy_dependencies.proto | 37 syntax = "proto2";
42 // See: http://go/proto2-generic-services-default
48 // We don't put this in a package within proto2 because we need to make sure
49 // that the generated code doesn't depend on being in the proto2 namespace.
|
| D | unittest_no_field_presence.proto | 35 // We want to test embedded proto2 messages, so include some proto2 types.
78 // N.B.: proto2-enum-type fields not allowed, because their default values
125 protobuf_unittest.TestRequired proto2 = 1; field
|
| D | unittest_import.proto | 37 syntax = "proto2";
39 // We don't put this in a package within proto2 because we need to make sure
40 // that the generated code doesn't depend on being in the proto2 namespace.
|
| D | map_proto2_unittest.proto | 31 syntax = "proto2";
36 // We don't put this in a package within proto2 because we need to make sure
37 // that the generated code doesn't depend on being in the proto2 namespace.
|
| D | unittest_proto3_arena_lite.proto | 87 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
88 // inside proto2 messages.
130 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
131 // inside proto2 messages.
|
| D | unittest_proto3_lite.proto | 86 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
87 // inside proto2 messages.
129 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
130 // inside proto2 messages.
|
| D | unittest_proto3_arena.proto | 86 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
87 // inside proto2 messages.
131 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
132 // inside proto2 messages.
|
| D | unittest_proto3.proto | 86 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
87 // inside proto2 messages.
131 // Omitted (compared to unittest.proto) because proto2 enums are not allowed
132 // inside proto2 messages.
|
| /third_party/protobuf/docs/ |
| D | implementing_proto3_presence.md | 4 proto3. Proto3 optional fields track presence like in proto2. For background
37 Presence in proto3 uses exactly the same syntax and semantics as in proto2.
38 Proto3 Fields marked `optional` will track presence like proto2, while fields
41 proto2.
44 3.11.4) it is not possible to use the same representation as proto2. Proto3
99 supports proto2, a proto3 `optional` field should use exactly the same API
100 and internal implementation as proto2 `optional`.
213 If your code generator does not currently support proto2, you will need to
223 If your code generator already supports proto2, then most of your work is
225 exactly the same API and behave in exactly the same way as proto2 optional
[all …]
|
| /third_party/protobuf/benchmarks/util/ |
| D | proto3_data_stripper.cc | 46 message = new benchmarks::proto2::GoogleMessage1; in main()
48 message = new benchmarks::proto2::GoogleMessage2; in main()
|
| D | gogo_data_scrubber.cc | 46 message = new benchmarks::proto2::GoogleMessage1; in main()
48 message = new benchmarks::proto2::GoogleMessage2; in main()
|
| /third_party/selinux/libsepol/src/ |
| D | ports.c | 193 int proto2 = c->u.port.protocol; in sepol_port_exists() local
197 if (proto == proto2 && low2 == low && high2 == high) { in sepol_port_exists()
231 int proto2 = c->u.port.protocol; in sepol_port_query() local
235 if (proto == proto2 && low2 == low && high2 == high) { in sepol_port_query()
|
| /third_party/protobuf/csharp/protos/ |
| D | unittest_import.proto | 37 syntax = "proto2";
39 // We don't put this in a package within proto2 because we need to make sure
40 // that the generated code doesn't depend on being in the proto2 namespace.
|
| /third_party/protobuf/src/google/protobuf/compiler/cpp/ |
| D | cpp_test_bad_identifiers.proto | 40 syntax = "proto2";
43 // See: http://go/proto2-generic-services-default
46 // We don't put this in a package within proto2 because we need to make sure
47 // that the generated code doesn't depend on being in the proto2 namespace.
|
| /third_party/protobuf/benchmarks/datasets/google_message2/ |
| D | benchmark_message2.proto | 33 // Benchmark messages for proto2.
35 syntax = "proto2";
37 package benchmarks.proto2;
|
| /third_party/protobuf/benchmarks/datasets/google_message1/proto2/ |
| D | benchmark_message1_proto2.proto | 31 // Benchmark messages for proto2.
33 syntax = "proto2";
35 package benchmarks.proto2;
|