Re: [gtkmm] Glib::ustring bug?

["Robert J. Hansen" <rjhansen inav net>]

> Please try data.c_str() before speaking of a bug. I suspect
> that the string returned by data.raw() is not '\0'-terminated.

Yes, .c_str() works properly.  However, if .raw() does not return a
string representation which works with third-party STL add-ons, I think
a word of warning somewhere in the documentation is appropriate. 
Otherwise, there's a reasonably good chance (given the popularity of
STLport) that people are going to want to use third-party STL in their
own applications, and may get surprised by the interactions their STL
implementation has with Gtkmm.

-- 
Geek Code: GAT d- s+:+ a27 C++(+++)$ ULB++>++++ P++ L+++>++++ E W+ N+ w
           PS+ PE++ Y++ PGP++ t+ 5++ X-- R tv b+++ DI++ D--- G+ e++ h*
           r* y+*