Gergely Nagy wrote: > I gave this some more thought, and there's a problem: while generating > riemann events and similar can be done with opaque types, if I do a > query, then I want to access the results, and to do that with opaque > types would mean I need a lot of getter functions (and an API + ABI > bump). So I'll stick to how it is done today, for the foreseeable > future. > > But I'll keep your suggestions in mind in case I end up writing another > library that uses protobuf, I'll hide the protobuf stuff deeper then! :)
Ah, OK, I did miss the fact that the protoc-c generated message structures get de-referenced. I am fairly sure that the layout of those structures has not changed in protobuf-c 1.0.0, but I will verify with abi-compliance-checker. The ProtobufCMessageDescriptor structures *have* changed, but I don't think you export those anywhere. -- Robert Edmonds edmo...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
