On Thu, Mar 14, 2019 at 3:02 PM Yann Ylavic <ylavic....@gmail.com> wrote:
> On Thu, Mar 14, 2019 at 8:38 PM William A Rowe Jr <wr...@rowe-clan.net> > wrote: > > > > On Thu, Mar 14, 2019 at 10:49 AM Yann Ylavic <ylavic....@gmail.com> > wrote: > >> > >> Possibly to resolve APR_<INTTYPE>_T_FMT on system with > >> [std]int[types].h, we could bind to the standard (C99?) format > >> PR[dxo..]N, especially since we configure the format based off > >> $ac_cv_sizeof_<inttype>, so something like: > >> #define APR_<INTTYPE>_T_FMT PR[dxo..]`expr $ac_cv_sizeof_<inttype>_t * > 8` > >> > >> That should work on most "modern" systems/compilers (including > >> -stdc=c89), no? And for older ones the current as fallback could be > >> reasonable. > > > > No, not with c89 (not as any sort of standard, -stdc is irrelevant.) > > Do you mean C89 only compilers which don't support C99+ (i.e. -stdc or > alike), and thus no inttypes.h and so on? > No, I mean, if you want to fall down that rabbit hole, be my guest, and I'll check out as a maintainer of our autocrap. Already sporting a killer headache of days in and out of the mechanics of WTF we have done to ourselves across configure.in and apr.h.in on Darwin in particular, w.r.t. both all the groups of LFS, apr_size_t and apr_off_t exceptions, glued together in different manners. Here's some encouragement towards your effort; http://clang-developers.42468.n3.nabble.com/libcxx-Platform-independent-printing-using-format-constants-td4027284.html Well, configure would work as today for them, and AIUI this is not on > those systems that we have an issue. > Right, so we leave the existing exception logic, bolting on more exception logic that may or may not trigger correctly depending on defines passed before including apr.h during ./configure vs. the user's project tooling. Sounds like a brilliant idea :)
