[erlang-questions] crypto deprecation warnings in latest release

Benoit Chesneau <>
Sat Jun 22 14:18:53 CEST 2013


I see a lot of deprecation warnings in the crypto module with the
latest release of Erlang. (crypto:sha_mac/2 -> crypto:hmac/3,
crypto_md5_* -> crypto:hash/2 ...) .

Is there a way to handle this changes at compile time to use latest
functions when possible and old functions in legacy releases?


With the help of rebar I did such change:

https://github.com/refuge/erlang-oauth/commit/2ab4a24c3f7db95b9ab43099ba1fa876a072e955

But I'm wondering if there is a better solution. Also able to handle
more legacy versions.

Any idea?

- benoit



More information about the erlang-questions mailing list