Hi,
due to organization changes and budget costs this task is put on hold.
Thank you for all your guidance up until now. If any further help is needed
regarding this issue in the future me or someone else will continue with
this thread.
On Thursday, 11 September 2014 20:00:52 UTC+2, Feng Xiao
Hi,
due to organization changes and budget cuts this task is put on hold. Thank
you for all your guidance up until now. If any further help is needed
regarding this issue in the future me or someone else will continue with
this thread.
On Thursday, 11 September 2014 20:00:52 UTC+2, Feng Xiao
I can't reproduce this outputting a 0x0; my example is below, and
outputs 22-0A-12-08-73-6F-6D-65-43-69-74-79 - the null nested message is
simply completely omitted; the contents are:
- 2 bytes field-header and length-prefix for the location member
- 2 bytes field-header and length-prefix for the
Just for visibility; we've discussed this more on github, and it *looks* to
be a protostuff decoding issue, not a protobuf-net encoding issue; Johannes
will take our findings to protostuff for further investigation.
Arbitrary link is
arbitrary:
For full visibility:
It turns out that the error was on my side. Apparently ProtoStuff can talk
different dialects. ProtoStuff and ProtoBuf.
It just depends on what IOUtil implementation you use.
When you read for instance, either use:
ProtobufIOUtil.mergeFrom(inputStream, t, schema, buffer);
Hello,
I am quite new to Protocol Buffers but I have read the tutorials. There is
one part of the encoding which I don't understand.
How the message types are encoded? As I see the tutorial mentions the field
encoding but the field id is unique only in the message.
Best regards,
Tamas
--
You
Hello,
I am quite new to Protocol Buffers but I have read the tutorials. There is
one part of the encoding which I don't understand.
How the message types are encoded? As I see the tutorial mentions the field
encoding but the field id is unique only in the message.
Best regards,
Tamas
--
You
On Wed, Oct 15, 2014 at 6:05 AM, Tamás Somhegyi
somhegyi.ta...@gmail.com wrote:
Hello,
I am quite new to Protocol Buffers but I have read the tutorials. There is
one part of the encoding which I don't understand.
How the message types are encoded? As I see the tutorial mentions the field
Updates:
Status: WontFix
Owner: xiaof...@google.com
Comment #10 on issue 447 by xiaof...@google.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
FYI.
Google's Style Guide now permits rvalue references to be used in move
constructors and
Comment #11 on issue 447 by chen3feng: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
Very disappointed to hear this message.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust
Comment #12 on issue 447 by cbsm...@gmail.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
Speaks volumes that after 22 months after submission and 5 months after a
working plugin was contributed, there isn't even a direct answer.
--
You received this
Comment #13 on issue 447 by chen3feng: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
let't make a fork on github?
2014-10-16 上午11:01于 proto...@googlecode.com写道：
--
You received this message because this project is configured to send all
issue
12 matches
Mail list logo
