/prebuilts/tools/common/m2/repository/com/google/protobuf/protobuf-java/3.0.0/include/google/protobuf/ |
field_mask.proto | 225 // SubMessage sub_message = 9;
|
/prebuilts/tools/darwin-x86_64/protoc/include/google/protobuf/ |
field_mask.proto | 173 // SubMessage sub_message = 9;
|
/prebuilts/tools/darwin-x86_64/protoc/include/google/protobuf/util/ |
field_mask_util.h | 159 // specified submessage fields that are missing in source will be cleared in
|
/external/protobuf/php/ext/google/protobuf/ |
upb.c | 130 "only length-delimited submessage fields may be lazy"); 221 /* All submessage fields are lower than all other fields. [all...] |
protobuf.h | 118 // submessage type is a map-entry msgdef).
|
storage.c | 197 // "Invalid type %s to assign to submessage field.",
|
upb.h | [all...] |
/external/protobuf/ruby/ext/google/protobuf_c/ |
upb.c | 173 "only length-delimited submessage fields may be lazy"); 264 /* All submessage fields are lower than all other fields. [all...] |
upb.h | [all...] |
protobuf.h | 334 // submessage type is a map-entry msgdef).
|
storage.c | 162 "Invalid type %s to assign to submessage field.",
|
/external/nanopb-c/generator/ |
nanopb_generator.py | 385 return None # Submessage size is indeterminate 387 # Include submessage length prefix 391 # Submessage cannot be found, this currently occurs when 392 # the submessage type is defined in a different file. [all...] |
/external/protobuf/csharp/src/Google.Protobuf/WellKnownTypes/ |
FieldMask.cs | 171 /// SubMessage sub_message = 9;
|
/external/protobuf/python/google/protobuf/internal/ |
message_test.py | 605 # Read nested message accessor without accessing submessage. 611 # Read accessor of nested message without accessing submessage. [all...] |
containers.py | 519 """Simple, type-checked, dict-like container for with submessage values."""
|
/external/protobuf/ruby/src/main/java/com/google/protobuf/jruby/ |
RubyMessageBuilderContext.java | 160 // repeated submessage field here with that type.
|
/external/nanopb-c/docs/ |
concepts.rst | 193 If the callback is used in a submessage, it will be called multiple times during a single call to `pb_encode`_. In this case, it must produce the same amount of data every time. If the callback is directly in the main message, it is called only once. 241 For example this submessage in the Person.proto file::
|
/external/nanopb-c/ |
pb_decode.c | 490 /* Clear a newly allocated item in case it contains a pointer, or is a submessage. */ 761 /* Initialize submessage to defaults */ [all...] |
/external/protobuf/js/binary/ |
reader_test.js | 151 // Reading past the end of a submessage should trigger an assertion. 819 // Add an int, a submessage, and another int.
|
/frameworks/base/location/java/android/location/ |
GnssNavigationMessage.java | 273 * <li> For GPS L1 C/A, BeiDou D1 & BeiDou D2, the submessage id corresponds to the subframe
|
/hardware/libhardware/include/hardware/ |
gps.h | [all...] |
/hardware/qcom/gps/msm8998/utils/ |
loc_gps.h | [all...] |
/hardware/qcom/gps/sdm845/utils/ |
loc_gps.h | [all...] |
/frameworks/base/media/java/android/media/ |
WebVttRenderer.java | [all...] |
/external/protobuf/python/google/protobuf/pyext/ |
map_container.cc | 693 "Direct assignment of submessage not allowed"); [all...] |