> On Apr 5, 2017, at 6:39 AM, Yann Ylavic <ylavic....@gmail.com> wrote: > > > Agreed, there seems to be few (if any) alternatives, though, but: > avoid using apr_proc/global_mutex_timedlock() on OSX is recommended. > Should we make it explicit with ENOTIMPL? >
Maybe we should reconsider the whole idea of timedlocks?? And besides, isn't the project called Apache *Portable* Runtime? Back when we started it this project, the idea was that if Platform Foo lacked a function we "needed", APR would provide it, not simply willy-nilly say "Nah, ENOTIMPL!". Sure, maybe it wasn't the "best" implementation, but we tried. That whole idea was to have each system/platform have some level of *parity*. Have we reversed that?
