mirror of
https://git.postgresql.org/git/postgresql.git
synced 2025-01-18 18:44:06 +08:00
e1d19c902e
Since our substitute snprintf now returns a C99-compliant result, there's no need anymore to have complicated code to cope with pre-C99 behavior. We can just make configure substitute snprintf.c if it finds that the system snprintf() is pre-C99. (Note: I do not believe that there are any platforms where this test will trigger that weren't already being rejected due to our other C99-ish feature requirements for snprintf. But let's add the check for paranoia's sake.) Then, simplify the call sites that had logic to cope with the pre-C99 definition. I also dropped some stuff that was being paranoid about the possibility of snprintf overrunning the given buffer. The only reports we've ever heard of that being a problem were for Solaris 7, which is long dead, and we've sure not heard any reports of these assertions triggering in a long time. So let's drop that complexity too. Likewise, drop some code that wasn't trusting snprintf to set errno when it returns -1. That would be not-per-spec, and again there's no real reason to believe it is a live issue, especially not for snprintfs that pass all of configure's feature checks. Discussion: https://postgr.es/m/17245.1534289329@sss.pgh.pa.us |
||
---|---|---|
.. | ||
ac_func_accept_argtypes.m4 | ||
ax_prog_perl_modules.m4 | ||
ax_pthread.m4 | ||
c-compiler.m4 | ||
c-library.m4 | ||
config.guess | ||
config.sub | ||
docbook.m4 | ||
general.m4 | ||
install-sh | ||
libtool.m4 | ||
llvm.m4 | ||
Makefile | ||
missing | ||
perl.m4 | ||
pkg.m4 | ||
prep_buildtree | ||
programs.m4 | ||
python.m4 | ||
tcl.m4 |