[erlang-questions] crypto deprecation warnings in latest release

[Benoit Chesneau]

I see :) Thanks!

On Sat, Jun 22, 2013 at 6:40 PM, ANTHONY MOLINARO
<anthonym@REDACTED> wrote:
> 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 <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:
>
> 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
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>