diff options
| author | Steve Vinoski <vinoski@ieee.org> | 2014-03-31 20:45:04 -0400 |
|---|---|---|
| committer | Steve Vinoski <vinoski@ieee.org> | 2014-03-31 20:49:09 -0400 |
| commit | cc3c2b546aff686dbc57eb9c4bc16956d22d045e (patch) | |
| tree | 5ee95f0332f5da59ff420f4eb52a6c9b51b3e261 | |
| parent | 219785005b451dec785179a9e6d5ee2e7551f2b1 (diff) | |
| download | erlang-cc3c2b546aff686dbc57eb9c4bc16956d22d045e.tar.gz | |
fix arity of crypto:hash_update/2 in deprecation warnings
When compiling code using deprecated crypto functions that should be
replaced with crypto:hash_update/2, the deprecation warnings were saying
"use crypto:hash_update/3", with the wrong arity of 3, instead of "use
crypto:hash_update/2".
The problem was reported in this email message to erlang-bugs:
http://erlang.org/pipermail/erlang-bugs/2014-March/004281.html
| -rw-r--r-- | lib/stdlib/src/otp_internal.erl | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/stdlib/src/otp_internal.erl b/lib/stdlib/src/otp_internal.erl index 971a2e2baa..b012c9f3f3 100644 --- a/lib/stdlib/src/otp_internal.erl +++ b/lib/stdlib/src/otp_internal.erl @@ -83,11 +83,11 @@ obsolete_1(crypto, sha_init, 0) -> {deprecated, {crypto, hash_init, 1}}; obsolete_1(crypto, md4_update, 2) -> - {deprecated, {crypto, hash_update, 3}}; + {deprecated, {crypto, hash_update, 2}}; obsolete_1(crypto, md5_update, 2) -> - {deprecated, {crypto, hash_update, 3}}; + {deprecated, {crypto, hash_update, 2}}; obsolete_1(crypto, sha_update, 2) -> - {deprecated, {crypto, hash_update, 3}}; + {deprecated, {crypto, hash_update, 2}}; obsolete_1(crypto, md4_final, 1) -> {deprecated, {crypto, hash_final, 2}}; |