Some linkers will drop object files that aren't referenced from anywhere, so if your code doesn't actually use anything from the .proto file defining the extension, it might not be linked in, and thus won't be in the registry. This is one of the common problems that make me wish we had an explicit ExtensionRegistry in C++... Otherwise, I don't know what your problem might be. If you can narrow it down to a small self-contained example I could debug it.
On Wed, Aug 26, 2009 at 3:04 PM, Jesper Eskilson <[email protected]> wrote: > On Wed, Aug 26, 2009 at 10:38 PM, Kenton Varda<[email protected]> wrote: > > In C++ all compiled-in extensions are automatically registered in a > global > > registry which is used automatically by all compiled-in classes. I now > > regret this design decision due to a number of subtle problems it > creates, > > but for you it means that you don't have to do anything special. > > I wonder why it isn't working for me, then. I'm serializing an object > from Java with an extension set, but when parsing it in C++, the > extension field is unset. I'll have to dig some deeper tomorrow. > > (Annoying time-zone lag. You're replying just around my bedtime. :-)) > > -- > /Jesper > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
