On Aug 3, 2010, at 16:44 , Julian González wrote:
I used the approach you mentioned and it worked. I just have a
problem I am writing 10,000 little messages in a file, first I write
the size of the message and then the message as it follows:
codedOutput-WriteVarint32(sample.ByteSize());
res
I have a message which describes an image:
message Image
{
required int32 width = 1;
required int32 height = 2;
optional string name = 3;
message Pixel
{
required int32 red = 1;
required int32 green = 2;
required int32 blue = 3;
optional int32 alpha = 4;
}
repeated Pixel pixels =
On Aug 4, 2010, at 9:50 , mark.t.macdon...@googlemail.com wrote:
Is there a way I can do this without creating a Pixel pointer?
Something like this (which doesn't compile):
Try fractal.mutable_pixel(0)-set_*
Hope this helps,
Evan
--
Evan Jones
http://evanjones.ca/
--
You received this
Comment #11 on issue 210 by ken...@google.com: Java code should detect
incompatible runtime library version
http://code.google.com/p/protobuf/issues/detail?id=210
Right. My point is that the so version isn't expected to relate to
anything else, whereas I suspect that the version on the
Status: New
Owner: ken...@google.com
Labels: Type-Defect Priority-Medium
New issue 211 by goo...@thenuthand.com: common.cc calls abort on FATAL
messages
http://code.google.com/p/protobuf/issues/detail?id=211
In stubs/common.cc there is a call to abort if a FATAL message is ever
recorded.
Updates:
Status: Accepted
Comment #1 on issue 211 by ken...@google.com: common.cc calls abort on
FATAL messages
http://code.google.com/p/protobuf/issues/detail?id=211
FATAL errors only happen in places that would otherwise crash. We do not
use exceptions in C++ code at Google.
I put together a TextMate bundle that highlights protocol buffer
syntax and avoids highlighting invalid syntax. The source is here:
http://github.com/michaeledgar/protobuf-tmbundle
It uses TextMate's nested highlighting rules to emulate the actual
parsing of the proto descriptor language. For
