Bug#127005: package is broken on arm, powerpc and s390 due to wrong assumption on char signedness
On Tuesday 01 January 2002 12:15, you wrote:
> These three are not necessarily bugs, though the code should be looked
> over to be certain.
>
I think these are bugs. See code fragments below.
if ((succ_index=T1_GetEncodingIndex( FontID, (char*) ligs->succ))==-1) {
/* successor is not current encoding */
ligs=ligs->next;
continue;
}
if ((lig_index=T1_GetEncodingIndex( FontID, (char*) ligs->lig))==-1) {
/* Specified ligature is not in current encoding */
ligs=ligs->next;
continue;
}
> > initialization of negative value `-1' to `char'
>
> Looks very bad. Would look even worse if I'd manage to find an actual
> occurrence in the reports. Please supply more information (source
> file & line, for example).
>
I didn't say that each warning occurs. I found the problem in about 300
packages and was not able to verify each warning for each package.
Regards,
Gerhard
Reply to: