Re: [Re: [gtkmm] gcc-3.3 and gtkmm-2.2.1]
- From: Chris Vine <chris cvine freeserve co uk>
- To: gtkmm-list gnome org, 192482 bugs debian org
- Subject: Re: [Re: [gtkmm] gcc-3.3 and gtkmm-2.2.1]
- Date: Mon, 19 May 2003 20:36:20 +0100
On Monday 19 May 2003 8:26 pm, Chris Vine wrote:
> On Monday 19 May 2003 1:50 pm, Christof Petig wrote:
> > B. Bell wrote:
> > > I won't be able to get to this until late monday, earlier if somebody
> > > wants to send a patch.
> >
> > I don't have a patch which implements the configure test but one which
> > unconditionally gives you a working gtkmm2 on debian again.
> >
> > BTW: Is hiding a typedef really worth the trouble of a configure check?
> >
> > Christof
>
> But does this actually work? (making struct Glib::ustring::SequenceToString
> public doesn't work for me). Putting the specialised nested class
> definitions directly in Glib::ustring removes all but two of the errors,
> but for two of the definitions (those with Glib::ustring::iterator as
> arguments) I get an error:
>
> specialization in non-namespace scope `class Glib::ustring'
>
> It seems to be more than just an access problem.
>
> Chris.
Cancel that, my mistake, it is an access problem. I needed to make the
declaration of both struct Glib::ustring::SequenceToString and of template
<class In, class ValueType = typename std::iterator_traits<In>::value_type>
public. When I do that, it works.
Chris.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]