Why not ? It seems reasonnable to want to use e.g. std::copy and friends.
On the documentation it says :
Most users will not ever use a RepeatedField directly; they will use the
get-by-index, set-by-index, and add accessors that are generated for all
repeated fields
What if I do want to
Yang writes:
currently Protocol Buffer parser moves down to the stream until it reaches end
of buffer,
but hadoop currently has a bug ( https://issues.apache.org/jira/browse/
MAPREDUCE-1487 ) that presents a buffer larger than the actual
message
to PB parser,
so PB parses
+kenton
Kenton may have a better answer, but I surmise that it's to avoid tying the
Reflection interface to implementation details. A Message implementation
might not use RepeatedField at all. The original version of protobufs used a
different class to represent repeated fields, so it wouldn't
Updates:
Labels: -Component-Docs
Comment #17 on issue 66 by ken...@google.com: cannot install using
easy_install
http://code.google.com/p/protobuf/issues/detail?id=66
I have no idea how that label got added to my previous comment.
--
You received this message because you are listed
Comment #18 on issue 66 by danhomerick: cannot install using easy_install
http://code.google.com/p/protobuf/issues/detail?id=66
Alright. What's the schedule for the next release? If there is one, that
is. =)
--
You received this message because you are listed in the owner
or CC fields of
Comment #19 on issue 66 by ken...@google.com: cannot install using
easy_install
http://code.google.com/p/protobuf/issues/detail?id=66
There's not a schedule. I'd imagine/hope it would happen within the next
couple
months, but can't guarantee anything.
I wish there were a way to test
