On 8/10/07, <b class="gmail_sendername">Michael Vanier</b> <<a href="mailto:mvanier@cs.caltech.edu">mvanier@cs.caltech.edu</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just to get the history right: garbage collectors have been around a _long_ time, since the '60s in<br>Lisp systems. They only became known to most programmers through Java (which is one unarguable good<br>thing that Java did).
</blockquote><div><br>Ah interesting :-)<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">As for threading, in addition to Haskell's approach you might also look at Erlang, which has a quite
<br>different (and quite interesting) approach to the whole problem. I wonder if anyone has tried to<br>implement a message-passing style of concurrency in Haskell.<br></blockquote></div><br>Erlang message passing rocks :-) I'd love to see this working in Haskell.
<br><br>Note that Erlang's message passing is not perfect. Specifically, there is zero type or parameter checking. It will quite happily let the following compile:<br><br>% initialization routines etc go here<br>% ...
<br><br>% ping thread. this sends messages to pong<br>ping() -><br> pong ! hello,<br> pong ! hello,<br> pong ! {hello}, % this does not throw a compile error<br> pong ! hello,<br> io:format("ping done~n" ).
<br><br>% pong thread, this listens for messages from pong<br>pong() -><br> receive<br> hello -><br> io:format("pong received hello~n"),<br> pong()<br> end.<br><br>You can see that sending the tuple {hello} does not cause a compile time error (or even a runtime error for that matter), even though pong does not have a valid pattern for receiving it.
<br><br>Now, arguably the fact that we are pattern matching on the receiver at least means we dont do anything with the invalid data sent, but this is not rocket science: the standard technique to ensure decent compile time validation in rpc-type things is to use an interface.
<br><br>The interface defines the method names and parameters that you can send across. Both the receiver and the sender have access to the interface definition, and it is trivial to check it at compile time.<br><br>(Caveat: havent looked enough into Erlang to know if there is a good reason for not using an interface?)
<br><br>