I don't know if this is interesting to you or not, but I've implemented a full protobuf parser in ply. I use that parser along with boost::python (you could convert this to SWIG without too much trouble I'm sure) to generate python wrappers for the C++ protocol buffer objects. Basically this means that you can create a protobuf object in C++ and look at it in python (or vice versa) without a serialize/deserialize step.
(If for some reason you need it, I can also autogenerate a protobuf to/from BSON serializer/deserializer as well.) Nate On Mon, Apr 22, 2013 at 2:48 PM, Andreas Hansson <[email protected]> wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1832/ > ----------------------------------------------------------- > > Review request for Default. > > > Description > ------- > > Changeset 9671:819570becef1 > --------------------------- > util: Auto generate the packet proto definitions > > This patch simplifies the usage of the packet trace encoder/decoder by > attempting to automatically generating the packet proto definitions in > case they cannot be found. > > > Diffs > ----- > > util/decode_packet_trace.py c5b24e8ed428 > util/encode_packet_trace.py c5b24e8ed428 > > Diff: http://reviews.gem5.org/r/1832/diff/ > > > Testing > ------- > > Ran encode and decode without existing packet_pb2 > > > Thanks, > > Andreas Hansson > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
