Alexander Perepelkin

DailyRollingFileAppender: more detailed documentation, added safety checks to implementation, refine tests

date appender and auto_link

date appender and auto_link

1) Similar functionality is implemented by DailyRollingFileAppender. 2) Native build systems are obsoleted in favor of CMake (autotools is present too)

logs using the %d format specifier were truncated too early Thanks, will keep in mind that there is an issue with implementation of internally shipped snprintf(). As for cross-compilation for a specific target architecture and relying on the standard snprintf() implementation, I assume that running ./configure with preset variable as shown above is an appropriate solution. In common cross-compilation scenario, there is no reliable way to verify whether standard snprintf() runs correctly on the target...

I'm not sure why the check was set up in the way it is. Does it really need to detect broken implementations of snprintf that return an incorrect value, or could a compile only check be enough? Here is an answer to why: https://www.gnu.org/software/autoconf/manual/autoconf-2.71/autoconf.html snprintf In C99 and later, if the output array isn’t big enough and if no other errors occur, snprintf and vsnprintf truncate the output and return the number of bytes that ought to have been produced. Some older...

Compiling failed on VC5

Use of format attribute with GNU compiler