This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: [gtkmm] Re: porting to libstdc++-v3 (<iostream.h> etc.)
- To: llewelly at dbritsch dot dsl dot xmission dot com
- Subject: Re: [gtkmm] Re: porting to libstdc++-v3 (<iostream.h> etc.)
- From: Karl Nelson <kenelson at ece dot ucdavis dot edu>
- Date: Mon, 17 Apr 2000 14:28:27 -0700
- cc: Benjamin Kosnik <bkoz at cygnus dot com>, Felix Natter <fnatter at gmx dot net>, libstdc++ at sourceware dot cygnus dot com, gtkmm-main at lists dot sourceforge dot net, kenelson at elm dot ece dot ucdavis dot edu
> 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.
Okay, where that is found please send a patch. Examples are
very hard to write because we don't want to clutter them up with
ifdefs as it blurs the use of the library, but if just doing an
include helps.
> 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.
Well, I recommend that we just use <iostream> and use a simple
kludge to make a fake iostream. However, this certainly won't work
with both installed. Gtk-- the library/headers should be safely
tested to figure out which you have and use it. (The examples
are a different story.)
> 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.
Havoc is not at this time associated with the Gtk-- project. He
developed on it some years ago but has since left. Every so often
he answers a question on the list or gets some renewed interest.
The current maintainers are myself (Karl Nelson) and Guillaume Laurent.
However, you will find the list to be far more helpful that either of
us directly. :-)
--Karl