[erlang-questions] crypto deprecation warnings in latest release
Sat Jun 22 23:52:20 CEST 2013
I see :) Thanks!
On Sat, Jun 22, 2013 at 6:40 PM, ANTHONY MOLINARO
> Something similar had to happen in mochiweb for R15 (where a bug in gen_tcp
> caused issues), it ended up looking similar
> So I think you came up with the best solution. Luckily after a few years
> you'll be able to remove the special
> cases :)
> On Jun 22, 2013, at 5:18 AM, Benoit Chesneau <bchesneau@REDACTED> 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:
> But I'm wondering if there is a better solution. Also able to handle
> more legacy versions.
> Any idea?
> - benoit
> erlang-questions mailing list
More information about the erlang-questions