Unlikely. I don't know how you'd implement GeneratedMessageReflection such
that it can deal with user-specified instances of basic_string.
On Mon, Apr 5, 2010 at 5:15 PM, skyork <sky...@gmail.com> wrote:
> I was wondering if there was any plans to support std::basic_string,
> as opposed to std::string? The reason I ask is because our code base
> uses a custom allocator for strings and hence our own string type
> (i.e. typedef std::basic_string<...> MyString), and the generated
> protocol buffer code is hard-coded against ::std::string. Even when I
> changed the outputted string type, a lot of the library I/O still only
> accepted std::string. It took a few more hours of compiler/library
> modifications to get that fixed up, and now everything seems to
> compile and run correctly, however all my delicate changes will be
> stomped in the next version release...
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to proto...@googlegroups.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to proto...@googlegroups.com.
To unsubscribe from this group, send email to
For more options, visit this group at