Re: porting to libstdc++-v3 (<iostream.h> etc.)

[llewelly at dbritsch dot dsl dot xmission dot com]

On Mon, 17 Apr 2000, Benjamin Kosnik wrote:

> > Of course I'd like to integrate these changes into the official version, so
> > I would appreciate any experience somebody may have:
> > for example, how should I decide whether ncurses++ (or Gtk--) should
> > be in std:: (and not just using ::std) ?
> 
> the only thing in std:: is the standard library.
> 
> Gtk-- is in Gtk::
> 
> > I am already working on converting ncurses++ (5.0) and Gtk-- (1.0.3).

Each use of 'you' below refers to Felix Natter, not Benjamin Kosnik.

1.0.3 is obsolete. You should switch to Gtk-- 1.2.0; it has a much
  improved interface, and seems to be less buggy.

This is especially true if you are going to be cleaning up any
  mis-interactions Gtk-- has with libstdc++-v3

I seem to remember that some of the Gtk-- examples assume <fstream>
  #includes <iostream> , which is not true in libstdc++-v3. 

I think some of the Gtk-- sources #include<iostream.h> and the like.
  If you are like me, and have both v2 and v3 installed, this will cause
  you a lot of difficulty, so go hunting for those .hs before you even
  compile.

Some parts of gtkmm use <strstream> . So make sure your libstdc++-v3
  snapshot or cvs checkout is recent enough to have <strstream> . 2.90.8
  or later? I can't remember.

> > Maybe someone on this list could look into the unstable Gtk-- ?
> > (I would have done it, but have not been able to find "libsigc++"..)

Currently, there is no unstable Gtk--. A few days ago, the Gtk-- 1.1.x
  development tree became 1.2.0, and was declared stable. I do not think
  the 1.3.x tree has started yet.

You can get libsigc++ from http://libsigc.sourceforge.net .
            Gtk--     from http://gtkmm.sourceforge.net   .

Last time I checked, libsigc++(0.8.6) compiled cleanly against
  libstdc++-2.90.7. However, I had to pass --disable-threads to configure.

I have not tried it, but I expect libsigc++ 1.0 will build cleanly against
  libstdc++ 2.90.8, and you may not need --disable threads.

> 
> I've talked to Havoc a bit about some of the issues. 
> 

For Gtk--, I suggest you use the mailing list at
  gtkmm-main@lists.sourceforge.net . By the way, I have cc'd this to that
  list.


[snip]