hello some comments:
strcasecmp does not exist when compiling with Visual Studio (_stricmp does though and is doing the same job). mingw-w64 use a #define for that.Why not adding ft_strcasecmp like ft_strdup ? note that using strdup with Visual Studio and passing _CRT_NONSTDC_NO_DEPRECATE removes the warning. Vincent Torri On Fri, Jul 24, 2020 at 5:02 AM David Turner <[email protected]> wrote: > > A better answer is to actually get rid of strcpy() / strcat() / sprintf() > because there will always be compilers complaining about them. > > Here's a patch that does that for freetype2-demos, please take a look. > > Le jeu. 23 juil. 2020 à 13:16, Werner LEMBERG <[email protected]> a écrit : >> >> > There seems to be a new warning in 2.10.2 (compared to 2.10.1) when >> > compiling for 32-bit: [...] >> >> Fixed in git, thanks. >> >> > Also have had a bunch of strncat related warning (probably gcc 1 specific, >> > or some compiler switch specific) in ft2-demos, for a while: >> > >> > === >> > inlined from 'RunIns' at src/ttdebug.c:2105:11: >> > /usr/include/bits/string_fortified.h:136:10: warning: >> > '__builtin___strncat_chk' output may be truncated copying 31 bytes >> > from a string of length 31 [-Wstringop-truncation] >> >> (The problematic calls of strncat are in function `Cur_U_Line'.) >> >> Hmm. The answer to >> >> >> https://stackoverflow.com/questions/50198319/gcc-8-wstringop-truncation-what-is-the-good-practice >> >> recommends to switch off the warning if the code does exactly ... >> >> >> Werner >>
