> Sorry, but we don't allow subclassing of protocol buffer objects (in any > language). Allowing this leads to too many "fragile base class" problems.
Sorry to bring up an old topic again, and I know it's discouraged, but I was wondering if there would be any incompatibilities if the subclass would remain very simple, simply adding a couple of custom member variables and otherwise only calling public functions in its own functions. Are there any binary structure dependencies that I'm not thinking of that would be broken(like the offsets table), or would this be a conservative enough subclassing? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
