Why do your protocol message types have to map 1:1 with your legacy classes?
Generally, attempting to map inheritance onto Protocol Buffers doesn't work
very well.
You are right that you can use extensions, but unless you have a large
number of subclasses of OParameter, this isn't helpful. If
Sorry, they are not implemented, but feel free to submit a patch.
On Wed, Aug 5, 2009 at 6:13 AM, jacobgladish jacob.glad...@sig.com wrote:
Does anyone know the current state of custom options with python? Are
they functional?
--~--~-~--~~~---~--~~
You
Currently there's no way to do that. You could add an option to
descriptor.proto, and update the Java code generator to honor it. Or you
could just use a postprocessing step like:
sed -i 's/^public class/class/' MyProto.java
On Wed, Aug 5, 2009 at 6:41 AM, v6ak vit...@gmail.com wrote:
How
Hi guys,
I was wondering if anyone out there had built an RPM spec file for
protobuf. I'll be needing to distribute the C++ runtime library to a
set of machines and I'd like to be able to chuck something in a shared
yum repo and be done with it, rather than having to copy around a
tarball or
