-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Christopher Faylor on 5/14/2007 6:25 AM: > Why do we need to export *vdprintf_r at all? Does some standard define it?
Does cygwin care about providing reentrant versions of functions? There is precedent for doing this: as an example, cygwin.din already exports asprintf_r. The *_r versions let the user provide a struct _reent* argument and manage the reentrancy themselves rather than relying on the automatic _REENT (aka _impure_ptr) reentrancy provided by cygwin. Furthermore, /usr/include/stdio.h already declares these functions as an underscore variant, so right now, you can link when using _asprintf_r. But I agree that no standard requires these reentrant variants, and that a user relying on _asprintf_r from /usr/include/stdio.h is already non-portable, so omitting these variants from cygwin.din does not bother me. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGSFpf84KuGfSFAYARAjPRAKCneWZH+m8FSjTyvt+vGuFEMZzoFQCdEXfs /37upuKPeZm5idVYMgJENuo= =L1DP -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
