Hi Jeff
It sounds like maybe you just want an application that works a bit like 'cabal'.
So with cabal the first argument is taken as the 'command' and then the rest
are based on that:
cabal build --some other --options --which may --or --may --not have --arguments
Yi has a simple template for
2008/10/17 allan [EMAIL PROTECTED]:
Hi Jeff
It sounds like maybe you just want an application that works a bit like
'cabal'.
So with cabal the first argument is taken as the 'command' and then the rest
are based on that:
cabal build --some other --options --which may --or --may --not
2008/10/17 Magnus Therning [EMAIL PROTECTED]:
I wanted to throw in another idea, something I didn't come up with
myself but used in omnicodec[1]. Now I don't remember where I picked
up the idea:
This method is described in
Hi,
I'm a slight Haskell newbie, but I'm trying to write a terminal-like
application that accepts simple commands with optional arguments, and
can then execute them. Most of these commands will need IO, as later I
will want to communicate over USB for most of them.
I was hoping, though,
Hi Jeff,
On Fri, Oct 17, 2008 at 01:29, Jeff Wheeler [EMAIL PROTECTED] wrote:
I'm a slight Haskell newbie, but I'm trying to write a terminal-like
application that accepts simple commands with optional arguments, and can
then execute them. Most of these commands will need IO, as later I will
Jeff Wheeler [EMAIL PROTECTED] wrote:
I suspect I should be using some sort of monad to represent the commands,
but I don't fully understand monads, and am not sure how it would apply in
this context.
Should I be using a monad here, and if so, how?
At risk of stating the obvious, you will
