Hi,
I asked this on GitHub but this seems to be the preferred place for asking
for help? :) https://github.com/google/protobuf/issues/973
I'm trying to integrate protobufs with an existing codebase that's
structured like
```
src/
python/
java/
thrift/
```
And I'm planning to add a
Im struggling to find a way of creating a generic Transaction packet, that
can encapsulate many transaction types. I was doing this with oneof but
oneof cannot be extended. Enums can't be extended either.
Im lost at this point for how to let one or more clients extend Transaction
and have
Hello all,
Has anyone tried to compile protobuf up for Xilinx's MicroBlaze processor?
I'm currently trying with their 2015.2 release, but configure fails due to
missing sched_yeild? (and no rt lib).
I've attached the config.log.
I'm building under Centos 6.7 64bit.
Mark
--
You received this
I really like using protobuf but I cannot find a way to make this one case
work.
I need to define a base, lets call it Transaction. Each message could be
implemented differently so my original implementation was
message Transaction{
oneof type {
NTx n = 1;
TTx tx = 2;
}
I have same problem now, and there is no uninitialized boolean attr
On Tuesday, February 7, 2012 at 11:45:29 PM UTC+8, Evan Jones wrote:
>
> On Feb 6, 2012, at 21:54 , Robby Zinchak wrote:
> > It turned out to be an uninitialized boolean. Properly setting the
> value in question seems to allow
One parameter method works fine if we start with proto and define the
services.
But, most of the code is usually evolved, For ex: Existing distributed java
services, who wants to use protobuf, instead of RMI/java-Serialization.
This feature is very useful in doing that.
On Tuesday, August
