Hi all. I was wondering if some people miss the colored output
of some applications, such like the IPython enhanced shell. I've
been googling for similar options for Haskell but I found nothing.
I feel that the type error messages, for example, would be a lot
more readable (or at least quicker to
Hi Neil,
Thanks for the pointer. From first skim-through at some PropLang library &
example code, I'm not seeing much similarity between the two systems.
GuiHaskell looks nifty. Cheers, - Conal
On 12/13/06, Neil Mitchell <[EMAIL PROTECTED]> wrote:
Hi,
> Thanks for your comments, Steve. T
Hi,
Thanks for your comments, Steve. They're getting me closer to a clear
explanation, which will be helpful in the paper I'm writing.
I was going to polish up PropLang before releasing it, but if you're
writing a paper, and I go and release PropLang just after you've put
the finishing touche
> I think I remember that some program was used to generate either the
> Hugs or GHCi ascii logo that appears when you fire up the interpreter.
While not being the same, there's a similar program in the Hugs demos
directory:
/usr/lib/hugs/demos/Say.hs
Say> putStr $ say "Hugs"
H H U U G
Push vs pull, rather than imperative vs functional, as the crux of the
inversion issue makes a lot of sense to me. And I see your point about
publish/subscribe removing the dependency inversion, while keeping a push
implementation and an imperative style. I also see how pull can be done
easily i
On Tue, 12 Dec 2006 17:54:26 -0800, you wrote:
>Notice that although, logically, the output depends on the input (being a
>rendering of its square), the code places into the input widget a dependency
>on the output widget, because the output widget contains the mutable state
>altered by the input
Nathan Mishra Linger wrote:
Dear Haskellers,
I think I remember that some program was used to generate either the
Hugs or GHCi ascii logo that appears when you fire up the interpreter.
__ __ __ __ ___
|| || || || || || ||_____ ___ _
