On 1 Nov, 16:39, Marcus Better mar...@better.se wrote:
I wonder if anyone has built libprotobuf-lite for the iOS, and if
there are any special pitfalls?
Yes I have, and of course I will share my findings with the world for
the benefit of mankind.
I also have a follow-up question: the
Greetings,
One of the best features of protocol buffers is the notion of presence.
Another great feature is the ability to do 'message.PrintDebugString()'.
One problem, however, is that fields which are not present do not get
displayed when printing the debug string.
Proposed solution: add an
On Tue, Nov 23, 2010 at 5:04 PM, Brenden Matthews bren...@diddyinc.comwrote:
Greetings,
One of the best features of protocol buffers is the notion of presence.
Another great feature is the ability to do 'message.PrintDebugString()'.
One problem, however, is that fields which are not
On Tue, Nov 23, 2010 at 3:47 AM, Marcus Better mar...@better.se wrote:
On 1 Nov, 16:39, Marcus Better mar...@better.se wrote:
I wonder if anyone has built libprotobuf-lite for the iOS, and if
there are any special pitfalls?
Yes I have, and of course I will share my findings with the world
Updates:
Status: Accepted
Owner: ken...@google.com
Comment #1 on issue 237 by ken...@google.com: potential portability problem
http://code.google.com/p/protobuf/issues/detail?id=237
(No comment was entered for this change.)
--
You received this message because you are
Comment #16 on issue 83 by ken...@google.com: protobuf does not compile
cleanly in 64-bit mode in Visual Studio 2008
http://code.google.com/p/protobuf/issues/detail?id=83
The code of those two functions did not change between 2.2.0 and 2.3.0, so
I'm not sure what you mean when you say
Hi Brenden,
Thanks for your interest in improving protocol buffers. I can see how this
option would be useful to some people. Unfortunately, there are a lot of
options that different people find useful, and if we implemented all of
them, we'd end up with a very boated library that no one wants
I see, the problem is that you've created a copy of descriptor.proto and are
extending that rather than extending the original file.
To correctly extend descriptor.proto, you need to import it like:
import google/protobuf/descriptor.proto;
The path name is important, because it determines
