[erlang-questions] crypto deprecation warnings in latest release

ANTHONY MOLINARO <>
Sat Jun 22 18:40:54 CEST 2013


Something similar had to happen in mochiweb for R15 (where a bug in gen_tcp caused issues), it ended up looking similar

https://github.com/mochi/mochiweb/commit/92b8f5bd10ce69d40005c8e78e52db9003f0189d

So I think you came up with the best solution.  Luckily after  a few years you'll be able to remove the special
cases :)

-Anthony

On Jun 22, 2013, at 5:18 AM, Benoit Chesneau <> wrote:

> 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
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130622/da6873b8/attachment.html>


More information about the erlang-questions mailing list