Greetings,
Apologies for the late thanks :) I'll work on this

On Thu, Mar 24, 2011 at 5:26 PM, Jason Hsueh <jas...@google.com> wrote:

> Apologies for the late response. Your plugin must write a valid
> CodeGeneratorResponse to stdout: protoc reads that response to modify the
> generated code. Your print statements are getting interpreted as part of the
> CodeGeneratorResponse and causing parse failures. For details, see:
> http://code.google.com/p/protobuf/source/browse/trunk/src/google/protobuf/compiler/plugin.proto
>
> On Sat, Mar 5, 2011 at 2:53 AM, Seref Arikan <serefari...@gmail.com>wrote:
>
>> Greetings,
>> I was experimenting with the test plugin source code that arrives with
>> protocol buffers, and I attempted to use cout to print out some values
>> from within the mock plugin.
>> The compiled plugin leads to an error from protoc, saying that plugin
>> output is unparsable, due to my use of cout.
>> cerr works fine, and so does printf. I've tried to find how cout is
>> redirected (and also why) to something other than the console.
>>
>> Any feedback would be much appreciated
>>
>> Regards
>> Seref
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Protocol Buffers" group.
>> To post to this group, send email to protobuf@googlegroups.com.
>> To unsubscribe from this group, send email to
>> protobuf+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/protobuf?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe from this group, send email to 
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en.

Reply via email to