[protobuf] Re: Issue 187 in protobuf: Command-line argument to override the optimize_for option

2010-07-28 Thread protobuf
Comment #11 on issue 187 by ken...@google.com: Command-line argument to override the optimize_for option http://code.google.com/p/protobuf/issues/detail?id=187 Hi all, Attached is a little protoc plugin written in Python which converts all the inputs to LITE_RUNTIME -- including renaming

[protobuf] Re: Issue 187 in protobuf: Command-line argument to override the optimize_for option

2010-07-28 Thread protobuf
Comment #12 on issue 187 by ken...@google.com: Command-line argument to override the optimize_for option http://code.google.com/p/protobuf/issues/detail?id=187 s/code code/core code/ s/retains/remains/ *sigh* -- You received this message because you are subscribed to the Google Groups

[protobuf] Re: Best practice to parse extensions in c++

2010-07-28 Thread Johan Philips
On 27 jul, 22:22, Kenton Varda ken...@google.com wrote: I agree, but we don't have a good API for querying which extension is set.  We might fix that someday by introducing language-level support for unions. Ok. So my struggle to find this API is more or less justified :-) for each

[protobuf] Issue 209 in protobuf: Binary file generated with protoc leads to an error message.

2010-07-28 Thread protobuf
Status: New Owner: ken...@google.com Labels: Type-Defect Priority-Medium New issue 209 by sebhub: Binary file generated with protoc leads to an error message. http://code.google.com/p/protobuf/issues/detail?id=209 What steps will reproduce the problem? 1. Download the attached files. 2. Run

[protobuf] why ParseFromIstream using std::cin always returns true using a pipe?

2010-07-28 Thread jetcube
I have a simple app that received data using the stdin and i have this loop: for(;;) { if(!request.ParseFromIstream(cin)) { cerr Cannot parse pb message. endl; return -1; } do_something(); } I wanted to test my app so i serialized a

Re: [protobuf] why ParseFromIstream using std::cin always returns true using a pipe?

2010-07-28 Thread Jason Hsueh
Messages without any required fields are allowed to have an empty serialization, so the library cannot assume that parsing empty input is an error. You just need to test cin.eof() separately. On Wed, Jul 28, 2010 at 7:18 AM, jetcube pmlo...@gmail.com wrote: I have a simple app that received

[protobuf] Re: Issue 209 in protobuf: Binary file generated with protoc leads to an error message.

2010-07-28 Thread protobuf
Updates: Status: WorkingAsIntended Owner: --- Comment #1 on issue 209 by jas...@google.com: Binary file generated with protoc leads to an error message. http://code.google.com/p/protobuf/issues/detail?id=209 The logging message is there to differentiate between parse failures

[protobuf] Re: why ParseFromIstream using std::cin always returns true using a pipe?

2010-07-28 Thread jetcube
Right, that is it! I think this explanation should be in the documentation :) (maybe it is but i didn't search hard enough) Thanks! On Jul 28, 6:34 pm, Jason Hsueh jas...@google.com wrote: Messages without any required fields are allowed to have an empty serialization, so the library cannot

[protobuf] libcurl integrtion

2010-07-28 Thread Birch
I am not well versed in c++, just a disclamer. I have muddled through creating a small client and I want to post the binary output via HTTP. Here is the source I have so far: #define CURL_STATICLIB #include iostream #include fstream #include string #include mvm.pb.h #include curl/curl.h