On Thu, Feb 5, 2015 at 9:52 PM, Rich Felker <[email protected]> wrote: >> And musl will eventually be forced to implement getpwent_r() >> if it wants to be usable for more packages... so... > > getpwent_r makes no sense;
The _r part does not make sense; the fact that it avoids static storage _is_ useful. > the _r functions are for thread-safe > versions of their corresponding legacy functions, but getpwent_r has > inherent global state -- the iterator. Whoever made it just wasn't > thinking. To make a correct interface like this the caller would need > to have an iterator object to pass to the function, but I can't see > much merit in inventing a new interface for this. It doesn't matter that it makes no sense. It's glibc compat. If you want more programs rather than less to build against musl, you have to strive to be glibc-compatible where practical. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
