Re: Multiple functions applied to a single value

2003-12-09 Thread Brandon Michael Moore
Control.Monad.Reader defines instances of Monad and MonadReader for ((->) r). Strangely enough, the documentation claims the Monad instance comes from Control.Monad, which is untrue. Here's the relevant chunk of the file. It looks like you came up with exactly the same code (modulo names). -- -

Re: Multiple functions applied to a single value

2003-12-09 Thread Derek Elkins
On Mon, 08 Dec 2003 16:33:53 + Graham Klyne <[EMAIL PROTECTED]> wrote: > A little while ago, I sent a long rambling message [1] containing a > key question in response to an earlier helpful response. I guess my > ramblings were quite reasonably passed over as too much waffle, and > the questi

Re: Multiple functions applied to a single value

2003-12-09 Thread Graham Klyne
A little while ago, I sent a long rambling message [1] containing a key question in response to an earlier helpful response. I guess my ramblings were quite reasonably passed over as too much waffle, and the question was lost. Here, I isolate the question. From the earlier response, I underst

Re: Multiple functions applied to a single value

2003-11-28 Thread Graham Klyne
At 21:03 27/11/03 -0500, Derek Elkins wrote: On Thu, 27 Nov 2003 14:56:03 + Graham Klyne <[EMAIL PROTECTED]> wrote: (perhaps a more serious and to the point reply later) > But not all cases I encounter involve lists or monads. A different > case might look like this: Are you sure this doesn't

Re: Multiple functions applied to a single value

2003-11-27 Thread Derek Elkins
On Thu, 27 Nov 2003 14:56:03 + Graham Klyne <[EMAIL PROTECTED]> wrote: (perhaps a more serious and to the point reply later) > But not all cases I encounter involve lists or monads. A different > case might look like this: Are you sure this doesn't involve monads? > > eval :: (b->c->d) -