Don't let gen_tcp:controlling_process/2 throw exceptions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Don't let gen_tcp:controlling_process/2 throw exceptions

Holger Weiß
The gen_tcp:controlling_process/2 and inet_sctp:connect/[45] functions
may (indirectly) call prim_inet:setopt/3.  Up to Erlang/OTP R16x, errors
returned by those prim_inet:setopt/3 calls were ignored.  Since 17.0, a
badmatch exception is generated if prim_inet:setopt/3 doesn't return ok.
This commit propagates the error to the caller, instead:

  git fetch git://github.com/weiss/otp.git propagate-setopt-error

Links:

  https://github.com/weiss/otp/compare/erlang:maint...propagate-setopt-error
  https://github.com/weiss/otp/compare/erlang:maint...propagate-setopt-error.patch

  https://github.com/erlang/otp/pull/674
_______________________________________________
erlang-patches mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-patches