[protobuf] Issue 650 in protobuf: Clang barks at file-options() != NULL

Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 650 by gli...@chromium.org: Clang barks at file-options() != NULL http://code.google.com/p/protobuf/issues/detail?id=650 With the ToT Clang the following warning is reported when I'm trying to build Chromium:

[protobuf] Re: Issue 269 in protobuf: Would like to have byte or int8 type for the message definition

Comment #4 on issue 269 by thecodem...@gmail.com: Would like to have byte or int8 type for the message definition http://code.google.com/p/protobuf/issues/detail?id=269 I don't need a fixed length string; I want to encode RGB or RGBA data as 3 or 4 bytes. I could pack them into an int32,

Re: [protobuf] Re: Issue 269 in protobuf: Would like to have byte or int8 type for the message definition

The simple answer would be use the existing oversized types, and cast at the caller. Varint data in particular will either be 1 byte or 2 (50% each) for byte values. For longer sequences (rgba etc) there are existing fixed-32 and bytes. If the intent is to add a wire type to precisely represent a