On Thu, Mar 24, 2016 at 9:31 AM, Yann Ylavic <ylavic....@gmail.com> wrote:
> >> nghttp2_session.c(160) : warning C4996: 'vsnprintf': This function or > >> variable may be unsafe. Consider using vsnprintf_s instead. To disable > >> deprecation, use _CRT_SECURE_NO_WARNINGS. > > [sarcasm] > Microsoft being unable to provide a safe vsnprintf() in the first > place and now warning every user is kind of ironic. > Microsoft claims that all the non-MS foo_s variants that have buffer targets as defined by POSIX are insecure, and offer foo_s variants. We have apr's safe strncpy etc, so it's not like we didn't agree - at least for some cases. They are free to make any claim they like, but they offered an out... from these warnings ... -D_CRT_SECURE_NO_DEPRECATE > Not to talk about they very personal conception of sizeof(long) on > 64bit systems... > You might be too young to remember when pointers had little to no relation to integer registers on many cpu architectures :) [/sarcasm] > > Not a very constructive comment, I agree :) > :)
