RE: [abc] oopsla outline

> I think of let() as a bit of a crutch that lets us express
> this kind of thing. A more natural way of talking about
> threads (even if it was just a pointcut primitive
> thread(Thread) with which you could bind the current thread)
> would have been preferable. Think of the syntactic solution
> Michael Martin mentioned in his reply to you -- that would
> have solved the problem without relying on let().

Certainly. I just fear that you would eventually end up with quite some
extensions of that kind. So I think that using let() is a very
consistent way actually because it only introduces one new construct
that lets you handle virtually all possible cases. I think future will
tell how useful it really is (or not).

Eric
Received on Tue Mar 07 22:26:51 2006