[gtkmm] Glib::ustring bug?

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

Glib::ustring does not play well with STLport, as I just found out by
sheer accident.  A short code snippet follows:


#include <string>
#include <iostream>
#include <gtkmm/main.h>

int main(void)
{
  Glib::ustring data("99999");
  std::cout << data.raw() << std::endl;
  return 0;
}


Compiling this with STLport 4.5.3 gives:

[rjhansen numbers rjhansen]$ g++ foo.cc `pkg-config gtkmm-2.0 --cflags
--libs` -I/usr/local/include/stlport -lstlport_gcc -lpthread -o foo
[rjhansen numbers rjhansen]$ ./foo
[rjhansen numbers rjhansen]$


Compiling this against my default RH-7.3 GCC-2.96 libs gives:

[rjhansen numbers rjhansen]$ g++ foo.cc `pkg-config gtkmm-2.0 --cflags
--libs` -o foo
[rjhansen numbers rjhansen]$ ./foo
99999


... I don't know if this is a known issue or not, but it's not mentioned
in the documentation either in "Programming with Gtkmm" or in the
Glib::ustring API ref.  If Glib::ustring doesn't work with commonly-used
STL implementations, it should probably be documented.


-- 
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+*