Re: 64-bit analysis of the gtk+ library
- From: Owen Taylor <otaylor redhat com>
- To: "Shivram U" <shivaram upadhyayula wipro com>
- Cc: <gtk-devel-list gnome org>
- Subject: Re: 64-bit analysis of the gtk+ library
- Date: Fri, 5 Jul 2002 11:50:49 -0400 (EDT)
"Shivram U" <shivaram upadhyayula wipro com> writes:
> I have generated the lint output of the gtk+ library for a 64-bit
> compilation environment. Would anyone be interested in the same. This would
> be useful in debugging potential 64-bit problems in a 64-bit environment.
If there are actual problems found by the lint output, we'd, of
course, be interested, and they should be filed in bugzilla but I don't
think we are particularly interested in the full output.
The general policy is that for GTK+/GDK/Pango we are not interested in
"problems" of the nature:
int foo = strlen (string);
unless there is some probability that the string could actually
usefully have 2 billion characters in it, and casts to suppress
64-bit lint warnings:
int foo = (int)strlen (string);
Are also not really acceptable, since they make the code much
more visually cluttered.
(We did go through and fix up GLib to be clean in the use
of size_t where necessary)
Also, no API changes that involve changing the width of arguments
can be made at this point.
(http://bugzilla.gnome.org/show_bug.cgi?id=56652 is a GTK+ bug that
was filed in this area earlier; the corresponding GLib bug is:
http://bugzilla.gnome.org/show_bug.cgi?id=53764.)
Regards,
Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]