(resend; forgot to copy the group) I have a somewhat cavalier approach, do I *do* support that in my implementation, but that is because my main audience is retrofitting to existing classes, or code-first; not contract first.
I won't get into a snare about whether that is right or wrong, but enough people wanted it, so I added t. The stream is still valid protobuf. If you want to get *really* upset, check my blog for the **other** impl-specific features I'm adding; reference tracking (full graphs, and string re-use) and object types not known in advance. I can feel the "tutting" already :) Marc On 17 Mar 2011, at 09:41, ctapobep <[email protected]> wrote: > So pity protobuf doesn't support inheritance, only because of this I > can't use it. Any forecasts, are creators going to add this feature? > > -- > 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. > -- 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.
