[9415] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: Was : Why is gtk+ written in C? - portability?
daemon@ATHENA.MIT.EDU (Owen Taylor)
Mon Oct 19 13:09:55 1998
To: Paul Miller <Paul_Miller@avid.com>
Cc: gtk-list@redhat.com
From: Owen Taylor <otaylor@redhat.com>
Date: 19 Oct 1998 13:20:32 -0400
In-Reply-To: Paul Miller's message of "Mon, 19 Oct 1998 13:00:06 -0400"
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
Paul Miller <Paul_Miller@avid.com> writes:
> > I thought this thread had died, but apparently not...
>
> It turned into a discussion of proper use of ANSI STANDARD "C" versus
> using compiler-specific extensions which undermine the portability of
> "portable" code. This is VERY important to gtk, and I think it is
> important to increase awareness of these issues.
>
> > Can we make it so?
>
> Just because gtk compiles fine with your compiler doesn't mean it's not
> a problem.
Well, OK.
But no patch to make GTK+ more ANSI compliant has ever been rejected,
GTK+-1.0.x compiles fine with -ansi -pedantic, and GTK+-1.2.0 will
too.
(Useful 'standard' extensions like 'inline' (in C9X) may be
configure-tested for but they will not be required.)
So, be assured, the ANSI versus non-ANSI discussion isn't useful.
Regards,
Owen
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
