Re: guchar -> gchar?

--===============0500021630==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-fgIqULLp278ZeTiS4CgP"


--=-fgIqULLp278ZeTiS4CgP
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, 2005-03-08 at 00:01 +0200, Lutz M=FCller wrote:=20
> Hello!
>=20
> Latest gcc produces lots of warnings like:
>=20
> gnome-print.c:738: warning: pointer targets in passing argument 1 of 'str=
len' differ in signedness
>=20
> the reason being gcc complaining about using unsigned char for standard s=
trings instead of char.
>=20
> Would it generate any problems elsewhere (compatiblity?) if we just
> changed the API from guchar* to gchar* for standard strings in a couple
> of places (namely gnome-print.h and gnome-print-config.h)?

It will likely cause lots of warning messages in existing code using
guchar* to call those functions! Note that the real cause of the
warnings that you see is _not_ that those functions expect guchar* but
that you (or whoever wrote the code) is passing to them gchar*.

Andreas=20
--=20
Prof. Dr. Andreas J. Guelzow
Dept. of Mathematical & Computing Sciences
Concordia University College of Alberta

--=-fgIqULLp278ZeTiS4CgP
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBC8AoiJ1WZh1HYgPsRAraXAJ0VmVdWwemIDSlVUHgdY//AFRTyTgCdEqWR
GX4e8aoUGpzguHrZE7dkbYg=
=H9Xk
-----END PGP SIGNATURE-----

--=-fgIqULLp278ZeTiS4CgP--


--===============0500021630==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gnome-print-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-print-list

--===============0500021630==--