Can I get a vote on apr-iconv in this respect? At 01:12 PM 6/25/2004, William A. Rowe, Jr. wrote: >I'm tempted to say we explicitly declare libapriconv as a private library of >libaprutil, just as the bundled expat is, with no public api support. That >simplifies things to simply @doxygenate the apr-iconv header to say >this is an internal api for use by apr-util, and pointing them to those >functions. > >The goal would be to allow us to redo the latest bsd-licensed iconv to >support other platforms, with or without apr, as an opaque dependency.
E.g. plugging in any iconv, even a non-iconv translation backend behind our apr-util's xlate API, would ensure nobody would 'count on' anything but apr-util apr_xlate_xxx to exist.
