<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>I have seen behaviours used in this way. All the behaviour contained was the behaviour_info/1 function which just returned the functions' name/arity. It was created for just this purpose. But it is not how behaviours were intended.<br><br>Robert<br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">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!<br>
<br><div class="gmail_quote">On Fri, Feb 17, 2012 at 3:03 PM, Tim Watson <span dir="ltr"><<a href="mailto:watson.timothy@gmail.com" target="_blank">watson.timothy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><div class="gmail_quote">On 17 February 2012 22:49, Jesse Gumm <span dir="ltr"><<a href="mailto:gumm@sigma-star.com" target="_blank">gumm@sigma-star.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I agree with you about the parameterised modules. I'm not a big fan<br>
of them either (though seeing how it works, I do understand why Rusty<br>
went that route), and the deprecation of the tuple modules had me<br>
scared for a moment. After that happened, I've been starting to think<br>
about a roadmap away from the parameterised modules with<br>
simple_bridge.<br>
<span><font color="#888888"></font> </span></blockquote></div><br></div><div>I think that's a good idea.</div><div><br></div><div>I would also like to respectfully suggest that api implementations might be distributed separately from the api itself, so that I can choose to get simple_bridge and simple_bridge_mochiweb (or whatever) but ignore the other stuff. Just a suggestion you may wish to consider.</div>
<div><br></div><div>Cheers,</div><div><br></div><div>Tim</div>
</blockquote></div><br>
<br>_______________________________________________<br>erlang-questions mailing list<br>erlang-questions@erlang.org<br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote><br></div></body></html>