On 2013-04-04 11:17 AM, Rafaël Carré wrote: > --- > mingw-w64-crt/lib32/msvcr100.def | 1 + > mingw-w64-crt/lib32/msvcr110.def | 1 + > mingw-w64-crt/lib32/msvcr80.def | 1 + > mingw-w64-crt/lib32/msvcr90.def | 1 + > mingw-w64-crt/lib32/msvcr90d.def | 1 + > mingw-w64-crt/lib32/msvcrt.def | 1 + > mingw-w64-crt/lib64/msvcr100.def | 1 + > mingw-w64-crt/lib64/msvcr110.def | 1 + > mingw-w64-crt/lib64/msvcr80.def | 1 + > mingw-w64-crt/lib64/msvcr90.def | 1 + > mingw-w64-crt/lib64/msvcr90d.def | 1 + > 11 files changed, 11 insertions(+)
Is this really a wise thing to do? _vsnprintf is not a POSIX-compliant implementation of vsnprintf, and IIRC, MinGW-w64 already implements its own compliant one in trunk. - Derek ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
