HI,
I have a bad solution. What I've been doing has been generating the .cc/.h
files, and then using doxygen to document those classes. You can document
C++ classes from files other than the header files that define the classes.
It's messy, error prone, and you end up with a lot of extra
I'm thinking of writing some scripting stuff, convert 'message' to
'struct' and stuff like that, and see how far I'll get with converting
proto files into some sort of pseudo-c. I think I'll mogrify the
'optional' and 'required' and 'repeated' flags to some custom doxygen
tags. As soon as I have
I have a C++ code that generates a buffer and sends it to a multicast
address, and Java based receiver that is supposed to get the buffer
and parse it. The problem I am facing is that after issuing
message.parseFrom(received_buf) or message.Builder.mergeFrom
(received_buf), I get the Error:
Never mind the question, I found out what the problem was. The buffer
defined for the datagram packet was clearly larger than what I was
expecting to get, and the parser was reading the whole buffer. Once I
copy that buffer to a temporary buffer, up to the number of bytes I am
receiving, and use