William A. Rowe Jr. wrote:

> As I mentioned, the actual contents of the structure are flexible IMHO.
> As a user, folks aren't expected to know the difference, but as a developer,
> something clearly labeled -alpha should be expected to be changing still.
> 
> So if a *developer* coded to any of these API's, well, all bets are off.
> 
> But we can leave the apr_crypto_driver_t at the same position as it was
> originally in the structure, no?

I plan to revert the entire change to v1.4 as you've requested, as
making apr_crypto_t private is definitely an incompatible ABI change
given that v1.4.x has been released.

I can then just focus on v2, where this problem can be fixed properly
for dbd and crypto (and then ldap).

Regards,
Graham
--

Reply via email to