Re: Bug#169450: wrong assumption on char signedness
# Anybody familiar with GLIB? I need help with this bug.
#
tag 169450 + help
thanks
On Sun, Nov 17, 2002 at 11:35:20AM +0100, Gerhard Tonn wrote:
[snip]
>
> Hi,
> char is per default unsigned on arm, powerpc and s390. There is a warning
>
> smurf.c:94: warning: comparison is always true due to limited range of data
> type
>
> during build of your package that might cause a runtime error. Please check
>
> http://buildd.debian.org/fetch.php?&pkg=smurf&ver=0.52.6-1&arch=s390&stamp=1035679798&file=log&as=raw
> for details.
[snip]
Hmm, I looked at the source code, and it seems that one of the arguments
being compared is a gchar (probably a char defined by GTK libs). Smurf
itself doesn't specify whether the variable is signed or not. Anybody
knows how gchar is supposed to behave? Should it be signed or unsigned?
This *may* be a bug in the GTK libs, although I think it should be
possible to work around in smurf.
T
--
Your inconsistency is the only consistent thing about you! -- KD
Reply to: