An example from http://code.google.com/apis/protocolbuffers/docs/proto.html
produces an error when fed into protoc:
$ protoc example.proto --cpp_out=.
example.proto:8:20: Expected "{".
example.proto:15:1: Reached end of input in message definition
(missing '}').
$ cat example.proto
message Outer
On Aug 19, 12:41 am, Marc Gravell wrote:
> The problem is the root certificate (CA Cert Signing Authority) - it
> certainly isn't in my trusted set of root certificates...
IMHO, browsers should have a way to do things like ssh does.
* Remember the certificate you got when you went go to a new
I notice that protoc can produce a nice descriptor set file and it
also has options to decode protobuf messages and will helpfully label
them for you if you give it the appropriate .proto file and message
type. But it won't helpfully label them for you if you give it a
descriptor set file, even t
