> On Dec 15, 2017, at 7:06 AM, Jim Jagielski <j...@jagunet.com> wrote: > > >> On Dec 13, 2017, at 2:49 PM, Ruediger Pluem <rpl...@apache.org> wrote: >> >> >> >> On 12/13/2017 04:27 PM, Steffen wrote: >>> I know, for example: >>> >>> util_expr_scan.c >> >> At least this one includes inttypes.h which seems according to the comments >> is only available on C99. >> Should we create an apr_uint8_t in apr and / or simply use apr_uint16_t in >> the uint8_t cases? >> > > I think we should create an ap_uint8_t while we wait for APR to > create an apr_uint8_t >
APR *does* have apr_byte_t, which some modules (like mod_proxy_ajp) use as a substitute for uint8_t Anyway, we have numerous places where we are using the uint*_t family. I've cleaned up the ones that affect backports and have updated STATUS as required.
