Re: [PATCH] [W32] Use SSIZE_T for ssize_t on Windows instead of long

--===============4868102504168396805==
Content-Type: multipart/signed; boundary="=BCCI_Security_Consulting_SCIF_Recall_Consul_H1N1_COCOT_Virual=Hemorr";
	micalg=pgp-sha512; protocol="application/pgp-signature"

--=BCCI_Security_Consulting_SCIF_Recall_Consul_H1N1_COCOT_Virual=Hemorr
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi!

On Tue, 19 May 2026 18:05, John Thacker said:
> 64-bit Windows uses a LLP64 data model, where long is still 32 bits and
> long long and pointers are 64-bits. The SSIZE_T Windows Data Type from
> basetsd.h is 32-bits on Win32 and 64-bits on Win64, and is intended for t=
he

Yeah.  That goes back to this patch

2010-07-09  Werner Koch  <[email protected]>

	* gcrypt.h.in [!__GNUC__ && W32]: Typedef ssize_t and pid_t to
	help building with MSVC.

I general we do not support building with MSVC but as one can see we
tried to help here.  Technically your patch is an ABI change when not
using gcc or clang (which for often critized reason also defines
__GNUC__) but assuming that building with MSVC on WIN64 anyway gives a
lot of warning, we could claim that this ABI change is a bug fix.

Thus I would accept it.  Other opinions?=20


Shalom-Salam,

   Werner

=2D-=20
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein

--=BCCI_Security_Consulting_SCIF_Recall_Consul_H1N1_COCOT_Virual=Hemorr
Content-Type: application/pgp-signature; name="openpgp-digital-signature.asc"

-----BEGIN PGP SIGNATURE-----

iJ8EARYKAEcWIQSHd0YfKgdOvEgNNZQZzByeCFsQegUCag1vPRsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMSwyLDINHHdrQGdudXBnLm9yZwAKCRAZzByeCFsQekA/AP91
mIM7dzQLyymflCiTjmgaWK7DADveRu1gv2JfzQoJAgD9E+Nr2utKD/kX5g3oa/oW
QlF848SF+lCiXgcPmx+5lAA=
=nd5Q
-----END PGP SIGNATURE-----
--=BCCI_Security_Consulting_SCIF_Recall_Consul_H1N1_COCOT_Virual=Hemorr--



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

_______________________________________________
Gcrypt-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gcrypt-devel

--===============4868102504168396805==--