We don't support this at this time - the primary problem is that specifying an allocator for C++ string's produces a completely new type. This means allocators can't simply be injected into a particularly message instance; instead it would have to be part of the message definition.
On Wed, Jul 6, 2011 at 6:28 PM, Gokul <gokul...@gmail.com> wrote: > Hi, > In the application, i am working on, we are managing the memory of > strings using allocators. But i find that the protobuf uses strings > without any allocator support. Is there a plan to provide allocator > support for strings in future? > Or can someone guide me on how to go about implementing this change? > > I would need a typedef somewhere to mention the string type and the > library should generate the appropriate code for it. > > Thanks, > Gokul. > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to protobuf@googlegroups.com. > To unsubscribe from this group, send email to > protobuf+unsubscr...@googlegroups.com. > 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 protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
