Mail Archives: cygwin/2007/05/14/08:25:44
On Mon, May 14, 2007 at 06:22:54AM -0600, Eric Blake wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>According to Corinna Vinschen on 5/14/2007 6:12 AM:
>>> _Exit
>>> dprintf
>>>
>>> There is also a big list of integer-only and reentrant variants of *printf that
>>> might be worth exporting:
>>>
>>> asiprintf, _asiprintf, asiprintf_r, _asiprintf_r, diprintf, _diprintf,
>>> diprintf_r, _diprintf_r, _dprintf, dprintf_r, _dprintf_r, fiprintf_r,
>>> _fiprintf_r, fprintf_r, _fprintf_r, iprintf_r, _iprintf_r, printf_r, _printf_r,
>>> siprintf_r, _siprintf_r, sniprintf, _sniprintf, sniprintf_r, _sniprintf_r,
>>> snprintf_r, _snprintf_r, sprintf_r, _sprintf_r, vasiprintf, _vasiprintf,
>>> vasiprintf_r, _vasiprintf_r, vdiprintf, _vdiprintf, vdiprintf_r, _vdiprintf_r,
>>> vdprintf, _vdprintf, vdprintf_r, _vdprintf_r, vfiprintf_r, _vfiprintf_r,
>>> vfprintf_r, _vfprintf_r, viprintf, _viprintf, viprintf_r, _viprintf_r,
>>> vprintf_r, _vprintf_r, vsiprintf, _vsiprintf, vsiprintf_r, _vsiprintf_r,
>>> vsniprintf, _vsniprintf, vsniprintf_r, _vsniprintf_r, vsnprintf_r,
>>> _vsnprintf_r, vsprintf_r, _vsprintf_r
>>
>> Why the underscore variants? Are they covered by any standard? If not,
>> we don't export these variants anymore. The existing ones have been
>> originally exported to maintain some compatibility to msvcrt, but this
>> is a moot point for a long time.
>
>I didn't realize that. No, there is no need for the leading underscore
>variants, which cuts the edits to cygwin.din in half (although recall that
>newlib provides, for example, only the pair vdprintf and _vdprintf_r, so
>cygwin.din needs to export vdprintf_r mapped to _vdprintf_r).
Why do we need to export *vdprintf_r at all? Does some standard define it?
cgf
--
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/
- Raw text -