<table cellpadding="0" cellspacing="0" class="GJVKSSSLV" role="listitem" style="border-style: initial; border-color: initial; width: 1285px; "><tbody style="border-style: initial; border-color: initial; "><tr style="border-style: initial; border-color: initial; "><td class="GJVKSSSKV" colspan="2" style="border-style: initial; border-color: initial; "><div class="GJVKSSSMV" role="article" tabindex="0" style="border-style: initial; border-color: initial; "><div style="border-style: initial; border-color: initial; ">Andrew,</div><div style="border-style: initial; border-color: initial; "><br></div><div style="border-style: initial; border-color: initial; ">>I think a lot of issues with APIs would be solved if we had something analogous to Java interfaces in Erlang.  Behaviors just don't cut it.  I want something that is a replica of interfaces.  Then all the Erlang guys have to do is create the interface and then people can create whatever implementations they want and I never have to worry about changing my code!</div><div style="border-style: initial; border-color: initial; "><br></div><div style="border-style: initial; border-color: initial; ">I think this new -callback stuff is more apt to solving the problem of interfaces.</div></div><div style="border-style: initial; border-color: initial; "></div><div style="border-style: initial; border-color: initial; "></div></td></tr><tr style="border-style: initial; border-color: initial; "><td align="right" colspan="2" style="border-style: initial; border-color: initial; "></td></tr></tbody></table><br><div class="GJVKSSSCT" style="border-style: initial; border-color: initial; "></div>