Re: clutter - "... int *argc" - their doc entries and corresponding GIArgInfo
David Pirotte <[email protected]> Sat, 11 May 2019 00:16:32 -0300
| Newsgroups | gmane.comp.gnome.language-bindings |
|---|---|
| Message-ID | <20190511001632.0fbfb8c9@capac> |
--===============2698220395956764900== Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/_dZHBYmfnu4nYpQV7SR.g=O"; protocol="application/pgp-signature" --Sig_/_dZHBYmfnu4nYpQV7SR.g=O Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable > I haven't been convinced, imo, the GIArgInfo, for argc, should always tel= l us > exactly what the C function argument is, in this case, in substance: I meant to write ... a GIArgInfo should always tell us exactly what the corresponding C function argument is ... argc is just an example of course > ... > type-tag =3D pointer > pointing-to =3D one-integer > ... > is-pointer? =3D #t > may-be-null? =3D #t > ... > gi-argument-field =3D v-pointer =20 Regards, David --Sig_/_dZHBYmfnu4nYpQV7SR.g=O Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEhCJlRZtBM3furJHe83T9k6MFetcFAlzWPpAACgkQ83T9k6MF etfItwf+Jf6DwXiXUGG4IId2r14Asc35w41Fq+sBxpebUW+aWnuXzpNL39iUlews KlBfkyhTE/zczEF+eAjfMtc6AZdWRtLs2vfxpwVmrc9gBsKXFv8Cg5htrNEOHXuS q6NBuCelztUWkD3sHtZPz5GwwUuD+EYe9s1HHi0AiKKa3CHdHqEg54B5csL2JLFX u/8EBDAqHNdd15K7mVSIMSYfUPXDrGnt7lNqgQXpVOAjMRVCKCge/m0b5qsxtMLy fN7JTNMny5K+t4Pzxl2j/diRBfPvd2xFcOscfPbJN4EKzwGJRYK3KjrDKNMZ2X24 Pw1Q5bhsUrYaWDXytv8swxtyKU6C5A== =1IjL -----END PGP SIGNATURE----- --Sig_/_dZHBYmfnu4nYpQV7SR.g=O-- --===============2698220395956764900== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ language-bindings mailing list [email protected] https://mail.gnome.org/mailman/listinfo/language-bindings --===============2698220395956764900==--