> > For humans, it is quite natural to use
> > visual cues (like layout) to indicate semantics.
I agree, but let us not try to do that with just two (already overloaded)
symbols.
> (let ((a 0)
> (b 1))
> (+ a b))
let { a = 0; b = 1; } in a + b
is valid Haskell and the way I use the language. Enough and more descriptive
visual cues, I say.
Using layout is an option, not a rule (although the thing is called layout
rule...)
> But all this is not very constructive, because Haskell is not going to
> change into a fully parenthesized prefix syntax at my wish.
Thank god :-)
Arjan
_______________________________________________
Haskell-Cafe mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/haskell-cafe
- RE: Functional programming in Python brk
- RE: Functional programming in Python Manuel M. T. Chakravarty
- Re: Functional programming in Python Erik Meijer
- RE: Functional programming in Python brk
- RE: Functional programming in Python Manuel M. T. Chakravarty
- Re: Functional programming in Python Ketil Malde
- RE: Functional programming in Python brk
- Re: Functional programming in Python Pertti Kellom�ki
- Re: Functional programming in Python Manuel M. T. Chakravarty
- Re: Functional programming in Python Kellomaki Pertti
- Re: Functional programming in Python Arjan van IJzendoorn
- Re: Functional programming in Python Paul Hudak
- Re: Functional programming in Python Kellomaki Pertti
- Re: Functional programming in Python Paul Hudak
- RE: Functional programming in Python brk
- Re: Functional programming in Python Dean Herington
- Re: Functional programming in Python Peter Hancock
- Re: Functional programming in Python Peter Hancock
- RE: Functional programming in Python Peter Douglass
- RE: Functional programming in Python Tom Pledger
- RE: Functional programming in Python S. Alexander Jacobson
