Re: [glade--]Re: [gtkmm] Problem with gtkmm handling comboboxes from glade
- From: Christof Petig <christof petig-baender de>
- To: murrayc usa net
- Cc: Daniel Elstner <daniel elstner gmx net>, John Bartelt <bartelt ics uci edu>, gtkmm mailing list <gtkmm-main lists sourceforge net>, glademm mailing list <glademm-list gnome org>
- Subject: Re: [glade--]Re: [gtkmm] Problem with gtkmm handling comboboxes from glade
- Date: Mon, 03 Dec 2001 11:33:08 +0100
Murray Cumming wrote:
> On Mon, 2001-12-03 at 09:32, Christof Petig wrote:
> > > I'd rather not risk breaking the ABI, or other code that uses SArray. If
> > > it can be fixed with a change to glademm then that would be better.
> >
> > I will not remove a sensible const (and ruin the generated code forever) because RH
> > shipped gcc-2.96.
>
> I have not followed this in detail, but this doesn't seem to be the same
> conclusion that was drawn last time this came up:
> http://marc.theaimsgroup.com/?t=100494551700001&w=2&r=1
>
> > I would tolerate a --for-gcc-2-96 command line switch (which might try to
> > auto-detect the compiler used). Are there any RH fans around which step ahead to
> > implement this?
>
> Wouldn't it be better to just use a std::vector? That would be clearer
> anyway.
Do you prefer
x.push_back("A");
x.push_back("B");
x.push_back("C");
over
{ "A", "B", "C" ... }
?
I do not.
Yes I agree it would be clearer. But it looks horrible to me (and considerung the
compiled code size, I would guess that the first variant is much bigger (inlining), but I
don't have numbers)
Christof
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]