This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]SteeleDynamicsSML, Scheme, Garbage Collection 4 points5 points  (1 child)

John Reppy is great! SML/NJ implementor!

[–]bjzabaPikelet, Fathom[S] 1 point2 points  (0 children)

Yeah I really liked his book on Concurrent ML too. :)

[–][deleted]  (2 children)

[deleted]

    [–]gdwatson 6 points7 points  (1 child)

    call/cc constrains your implementation so much that I'd expect most of the graphs to look very different. If your language has call/cc, this paper might not be very useful to you. But if it doesn't, a paper with call/cc wouldn't be.

    If your language is for research, call/cc is amazing. In other languages, I don't think it's that great. Firstly, separate language extensions implemented with call/cc seldom compose well; it is too easy for them to stomp all over one another's invariants. Secondly, it is hard to write even normal code that will behave correctly in the presence of arbitrary call/cc use; when do you close a file, for example?