Fair enough.
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/protobuf/-/7gP8hw2OQEsJ.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe fr
Quote: >>
Foo foo;
foo.SetExtension(bar, 15);
Similarly, the Foo class defines templated accessors HasExtension(),
ClearExtension(), GetExtension(), MutableExtension(), and AddExtension().
end quote <<
To re-write the sentence: "Similarly to the SetExtension() mentioned in the
above example, the F
Silly me. Of course. I can't believe I missed that. Thanks.
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/protobuf/-/6Sc6zkWd8HkJ.
To post to this group, send email
So should SetExtension() be explicitly listed in the Language Guide, or
not?
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/protobuf/-/cij0Z7Gnvn4J.
To post to this
See my response in the other thread. You can set label to the
FieldDescriptorProto.
On Tue, Jul 26, 2011 at 12:31 AM, Giancarlo Frison wrote:
> Hi all,
>
> I'm attempting to create descriptors dynamically for generating custom
> message on the fly.
> The trouble is when I have to describe a field
The SetExtension() is mentioned in the example. The accessors mentioned in
the following paragraph are "similar" to the SetExtension template function.
On Mon, Jul 25, 2011 at 5:07 PM, Chris Morris wrote:
> Should the Extensions section in the Language Guide (
> http://code.google.com/apis/protoc
I didn't see any test failures from your log:
[==] 764 tests from 102 test cases ran. (3249 ms total)
[ PASSED ] 764 tests.
The ERROR logs are expected, to test the protoc complains in some
situations.
On Mon, Jul 25, 2011 at 2:28 PM, Chris Morris wrote:
> So I downloaded the source t
Not sure if I understand your question correctly. You can set the label in
FieldDescriptorProto:
LABEL_OPTIONAL = 1;
LABEL_REQUIRED = 2;LABEL_REPEATED = 3;
On Tue, Jul 26, 2011 at 12:21 AM, Giancarlo Frison wrote:
> There is this example that I'm approaching to re-implement
> http://
There is this example that I'm approaching to re-implement
http://flori.posterous.com/dynamically-creating-protocol-buffer-objects
a question:
How to handle repeated fields? How can you describe them in the
fieldDescriptor?
On Jul 18, 5:20 pm, yoave wrote:
> Hi all,
>
> I've got 2 questions:
Hi all,
I'm attempting to create descriptors dynamically for generating custom
message on the fly.
The trouble is when I have to describe a field as 'repeated' and
dynamically serialize and parse it.
How define 'repeated' fields?
This is how I create such descriptors (http://flori.posterous.com
10 matches
Mail list logo