<html><head></head><body bgcolor="#FFFFFF"><div>The popularity of a language has no bearing on the quality of one of its features. Are there other message passing schemes you prefer?<br><br>Sent from my iPhone</div><div><br>On Jan 22, 2012, at 5:53 AM, Manu <<a href="mailto:turkeyman@gmail.com">turkeyman@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div class="gmail_quote">On 22 January 2012 15:18, Jacob Carlborg <span dir="ltr"><<a href="mailto:doob@me.com">doob@me.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">On 2012-01-21 19:35, Manu wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On 21 January 2012 18:09, Sean Kelly <<a href="mailto:sean@invisibleduck.org" target="_blank">sean@invisibleduck.org</a><br></div><div class="im">
<mailto:<a href="mailto:sean@invisibleduck.org" target="_blank">sean@invisibleduck.org</a><u></u>>> wrote:<br>
<br>
I suggest checking out Erlang messaging, as it's the basis for this<br>
design. Maybe then things will be a bit clearer.<br>
<br>
<br>
Are you suggesting that erlang is a common language that all programmers<br>
worth their paycheques are familiar with... and would also find intuitive?<br>
I don't know if it's the most sensible API decision to model a design<br>
off something so obscure, unless you suspect that D should appeal<br>
primary to ex-erlang users?<br>
<br>
Just to re-iterate, I'm not arguing against the API or it's merits, it's<br>
really cool, just that it shouldn't be the trivial one named receive().<br>
That name should be reserved for the most conventional API.<br>
</div></blockquote>
<br>
Scala also uses a similar API as Erlang.</blockquote><div><br></div><div>Another super-mainstream language that everyone's familiar with :)</div></div>
</div></blockquote></body></html>